Method and apparatus for installing an application onto a smart card

ABSTRACT

An application identifier (AID) comprises at least one customization parameter for an application to be installed onto a smart card. The application may be installed onto the smart card by providing the AID, instantiating the application onto the smart card, storing the AID onto the card, and configuring the application in accordance with the stored AID, wherein the application is configured in accordance with the at least one customization parameter.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to the following:

-   -   U.S. patent application Ser. No.________, filed Feb. 24, 2004 in         the name of inventor Eduard K. de Jong, entitled “Method and         Apparatus for Providing an Application on Smart Card”, Attorney         Docket No. SUN-P9176, commonly assigned herewith;     -   U.S. patent application Ser. No.________, filed Feb. 24, 2004 in         the name of inventor Eduard K. de Jong, entitled “Method and         Apparatus for Selecting a Desired Application on a Smart Card”,         Attorney Docket No. SUN-P9178, commonly assigned herewith; and

U.S. patent application Ser. No.________, filed Feb. 24, 2004 in the name of inventor Eduard K. de Jong, entitled “Method and Apparatus for Processing an Application Identifier from a Smart Card”, Attorney Docket No. SUN-P9179, commonly assigned herewith.

FIELD OF THE INVENTION

The present invention relates to the field of computer science. More particularly, the present invention relates to installing an application onto a smart card.

BACKGROUND OF THE INVENTION

Most people now have a collection of small plastic cards, representing various credit cards, store cards, identity cards, membership cards, and so on. Information about the card and its owner, such as account details and so on, is normally printed or embossed on the card, and may also be stored in some form of magnetic strip. Note that such cards are simply passive storage devices, and the information that they contain is fixed at card creation time.

In recent years, smart cards have also proliferated. These are similar in scale to traditional credit cards, but incorporate within their plastic cases a microelectronic memory and also (optionally) an embedded processor. It will be appreciated that the computational resources available within a smart card are extremely limited compared to those of a desktop workstation, or even a laptop or handheld device. One especially popular form of smart card is known as a Java Card. This is based on the Java platform developed by Sun Microsystems (“Java” and “Java Card” are trademarks of Sun Microsystems Inc). In such devices, a Java virtual machine (VM) is provided within the smart card to allow the execution of Java applets or applications. Particular advantages of being able to use the Java environment for smart card applications are the inherent security features of the Java environment, plus the ready availability of software development packages for the Java programming language. It is estimated that by the end of 2002 over 200 million Java cards had been shipped. More information about the Java Card smart card platform is available from the page: /products/javacard/ at the web site: http://java.sun.com and from the site: http://wwwjavacardforum.org/.

An Application Programming Interface (API) is defined for the Java Card platform. Applications written in the Java programming language invoke this API to access the Java Card run-time environment (JRE) and any native services. The Java Card API allows application portability, in that the same application can run on any smart card that supports the API. The Java Card API is compatible with international standards, in particular the ISO/IEC 7816 family of standards.

Note that programs that run on smart cards may be referred to as either an application or as an applet. It will be appreciated that there is a clear distinction between a Java applet and a Java application in a desktop environment, in particular the absence of a main class from the former. However, this distinction does not apply in the smart card environment. Thus applets for use on a Java card platform are not the same as applets that run on a web browser. The term applet will generally be used herein to refer specifically to code, and the term application to refer to the higher level functionality provided by the applet code and associated data (unless the context requires otherwise).

The Java Card platform supports multiple applications on a single card. These may be separated by firewalls, in order to ensure that they do not interfere with one another. This is particularly of concern if the various applications are operated by different organizations, whose business relationships with the cardholder may be independent of one another.

FIG. 1 is a high-level schematic diagram illustrating the main architectural components in a typical smart card application. In particular, smart card 102 belonging to cardholder 101 interacts with a terminal 110 by exchanging an application protocol data unit (ADPU) 108. The format for the ADPU is defined by the International Standard ISO/IEC 7816-3.

Terminal 110 may be a handheld device, an adjunct to a desktop workstation, a dedicated card reader (analogous to an ATM) or any other suitable system. Furthermore, the communications between the smart card 102 and the terminal 110 may be by wired connection, such as some form of bus (e.g. USB), or by wireless link (e.g. radio or some other electromagnetic signal), depending on the particular devices concerned. In addition, the terminal 110 may be under the direct control of an operator 111 (such as for a handheld terminal), or alternatively terminal 110 may be automated (such as for an ATM).

Terminal 110 interacts with a back office 130 over any suitable form of network 120, such as the Internet, a local area network (LAN), a wide area network (WAN), and so on. Back office 130 may comprise multiple systems (not explicitly shown in FIG. 1), such as a web server or portal attached to network 120, perhaps with an application server and/or a database system behind. Note that the terminal 110 may be off-line until activated by a smart card 102, a card holder 101 or a terminal operator 111 to access a back office 130 over network 120.

In operation, the cardholder 101 typically places the card 102 into or adjacent to the terminal 110, thereby allowing the two to interact, e.g. to perform a debit operation from the card, in order to purchase some goods. This interaction will generally be referred to herein as a session, and typically involves the exchange of multiple messages between the smart card 102 and the terminal 110. A session can be regarded as comprising multiple transactions, where each transaction represents the completion of some portion of the overall session (e.g. a security authorization).

Associated with each applet on smart card 102 is an Application Identifier (AID). The AID is a byte string up to 16 bytes long, whose format is defined by International Standard ISO/IEC 7816-5. Thus according to this standard, the first 5 bytes of the AID represent the registered application provider identifier (RID) and have a value allocated by ISO or one of its member bodies. The RID generally indicates the merchant or other entity involved with operating the applet, hereinafter referred to as the RID operator. The RID operator is generally responsible for the back office program 130, and is depicted as application/RID operator 131 in FIG. 1. The last 11 bytes of the RID constitute the proprietary application identifier extension (PIX). The PIX is determined by the RID operator 131, and can be used to store a reference number or other information associated with the applet.

FIG. 1A illustrates the storage of the AID on a typical smart card 102. The AID bytes are stored in a byte array, which represents internal storage for a Java AID object 161. Applications can therefore access the AID by making appropriate calls to AID object 161, which in effect provides a wrapper for the underlying byte array.

International standard ISO/IEC 7816-4 defines a procedure to allow a terminal to locate a desired application on a smart card, and this is illustrated at a high level in the flowchart of FIG. 1B. The procedure starts when the smart card 102 is first inserted into the terminal 110. The terminal detects the insertion of the smart card (reference numeral 162), and in response to such detection activates the smart card (reference numerals 164, 172). This activation typically includes providing power to the smart card.

The terminal now sends a request using an application protocol data unit (ADPU) 108 to the smart card (reference numeral 166). The ADPU identifies the application to be used in this session in terms of its AID. The request from the terminal is received by the smart card (reference numeral 174), typically within an applet selector program that is running on the smart card 102 as part of a card executive layer. The applet selector is then responsible for locating and launching the application that matches the AID request from the terminal, i.e. the application that has the same AID as specified in the request (reference numerals 176 and 177). The smart card also returns the AID for the matching application back to the terminal 110 (reference numerals 179 and 180). (N.B. Reference numerals 179 and 180 are optional within the context of ISO/IEC 7816-4, although commonly implemented).

FIG. 1C describes a variation on the above approach (also in accordance with ISO/IEC7816-4), in which the terminal 110 supplies the card with a truncated AID (known as a partial AID), for example the first ten bytes of an AID. In these circumstances, there may be multiple matches against the partial AID. For example, if two applets have AIDs that have the first ten bytes in common, and then differ only in the final six bytes of the AID, they will both match the same partial AID of length 10 bytes (or less). One reason for using a partial AID might be if the terminal 110 wants to identify all applets on the card having a particular RID.

The processing of FIG. 1C commences as just described for FIG. 1B, except that at reference numeral 166 the request from the terminal 110 to the smart card 102 comprises only a partial AID. Consequently, the smart card may identify multiple matching applications at reference numeral 176. The AIDs for these matching applications are then returned to the terminal 110 (reference numerals 179, 180), in order to allow the terminal (or user) to select a specific desired application from those matching the partial AID. Thus the terminal now sends a request to the smart card to launch an applet (reference numeral 182). This request specifies the particular applet to be launched on the smart card in terms of its complete AID (generally selected from the set of those received from the smart card at reference numeral 180). The smart card duly responds to this request by launching the applet selected by the terminal (reference numeral 190).

In fact, the skilled person will realize that although FIG. 1C represents an appropriate logical model for the use of partial AIDs, the actual implementation looks more like FIG. 1B (primarily for historical reasons). Thus current systems generally accommodate the matching and return of multiple matching AIDs by identifying only a single matching AID at a time. In particular, the applet having the AID that is first matched to the partial AID received from the terminal is launched, and the complete AID for this applet is returned to the terminal 110. The smart card then only supplies a next matching AID upon a subsequent specific request from the terminal. Nevertheless, it will be appreciated that multiple matching AIDs could be handled in other ways, such as by returning the complete set of multiple matching AIDs all at once in a single response to the terminal (as depicted in FIG. 1C).

FIG. 2 is a schematic diagram representing the life cycle of a smart card, which in this particular implementation is a Java Card. This life cycle commences with the manufacture of the card, and the initial loading of the base operating system and the Java Card environment (reference numeral 210). Also at this stage, one or more applications may be preloaded (reference numeral 215). Generally, the base operating system and Java Card environment, and also potentially any preloaded applications, may be stored in ROM on the smart card 102 as part of the manufacturing process.

The card is now ready for issue to a cardholder (reference numeral 220), which typically involves an appropriate personalization process, as well as initialization of the Java environment, and starting the Java virtual machine on the card. The cardholder is thereafter able to use the card (reference numeral 230), such as in the manner illustrated schematically in FIG. 1. Note that if the card was originally issued without any preloaded applications, then the cardholder may have to load an application prior to making substantive use of the card. In practice however, this situation is rather uncommon, since usually there is at least one preloaded application in order to motivate issuance of the card in the first place.

During the operational lifetime of the card, further application programs may potentially be installed onto the card (reference numeral 235), for example if the cardholder signs up to new accounts or services. Conversely, applications may be removed from the card, perhaps because an account is closed.

The last operation shown in FIG. 2 is where the card is terminated (reference numeral 240). This may occur, for example, because the card has a built-in expiry date or is surrendered by the user (perhaps if the user is moving to a new card issuer, or the card is physically damaged).

Although the Java Card environment does support multiple applications from different RID operators, nevertheless, in practice, the installed applications on a large majority of issued cards come from and are run by a single RID operator. In other words, applications from one RID operator are typically found on one card, and applications from another RID operator on a different card. Consequently, relatively little attention has been paid to the business and technical problems associated with the provision and utilization of multi-vendor smart cards.

SUMMARY OF THE INVENTION

An application identifier (AID) comprises at least one customization parameter for an application to be installed onto a smart card. The application may be installed onto the smart card by providing the AID, instantiating the application onto the smart card, storing the AID onto the card, and configuring the application in accordance with the stored AID, wherein the application is configured in accordance with the at least one customization parameter.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention.

In the drawings:

FIG. 1 is a schematic diagram illustrating the main components involved in a typical smart card application.

FIG. 1A is a schematic diagram representing the implementation of an AID object in a typical existing smart card.

FIG. 1B is a flowchart whereby a terminal selects and launches one application out of potentially multiple applications on a smart card by providing a full AID to the smart card.

FIG. 1C is a flowchart whereby a terminal selects and launches one application out of potentially multiple applications on a smart card using partial AID matching.

FIG. 2 is a schematic diagram illustrating the typical life cycle of a smart card.

FIG. 3 is a schematic block diagram representing at a high level the structure of a typical smart card.

FIG. 4 is a schematic diagram illustrating the interaction between a smart card and a terminal in accordance with one embodiment of the invention.

FIG. 5 illustrates the composition of an AID in accordance with one embodiment of the invention.

FIGS. 5A, 5B, 5C, and 5D illustrate the structure of an AID interpreter in accordance within certain embodiments of the invention.

FIG. 6 is a flowchart depicting a procedure for matching an applet on a card in accordance with certain embodiments of the invention.

FIGS. 6A through 6E are flowcharts illustrating in more detail the procedure of FIG. 6 in accordance with various embodiments of the invention.

FIG. 6F is a flowchart depicting a procedure for matching in the terminal an applet on a card in accordance with one embodiment of the invention.

FIG. 7 is a flowchart illustrating a smart card dynamically generating an AID to provide to a terminal in accordance with one embodiment of the invention.

FIG. 8 illustrates a procedure for a terminal to utilize an AID to obtain code or information to support processing the AID in accordance with one embodiment of the invention.

FIGS. 8A through 8F illustrate aspects of the processing of FIG. 8 in more detail for various embodiments of the invention, comprising some of the processing performed at a server.

FIG. 9 illustrates the server processing for a request from a terminal in accordance with one embodiment of the invention.

FIGS. 10 and 11 are schematic diagrams of the components involved in utilizing an AID to obtain code or information to support processing the AID in accordance with two different embodiments of the invention.

FIG. 11A illustrates the use of a default proxy AID interpreter in accordance with one embodiment of the invention.

FIG. 12 is a flowchart illustrating a procedure for a terminal to obtain a set of AIDs from a smart card in accordance with one embodiment of the invention;

FIG. 12A is a flowchart illustrating some of the operations of the procedure of FIG. 12 in more detail in accordance with one embodiment of the invention.

FIG. 13 is a flowchart illustrating a procedure for a terminal to identify a matching application in accordance with one embodiment of the invention.

FIG. 13A is a flowchart illustrating the selection of proxy program on the terminal in accordance with one embodiment of the invention.

FIG. 14 is a flowchart illustrating the installation of an application comprising an AID onto a smart card in accordance with one embodiment of the invention.

FIG. 15 is a flowchart illustrating the use of the AID to hold configuration data in the flowchart of FIG. 14.

DETAILED DESCRIPTION

Embodiments of the present invention are described herein in the context of installing an application onto a smart card. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.

In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.

In accordance with one embodiment of the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems (OS), computing platforms, firmware, computer programs, computer languages, and/or general-purpose machines. The method can be run as a programmed process running on processing circuitry. The processing circuitry can take the form of numerous combinations of processors and operating systems, or a stand-alone device. The process can be implemented as instructions executed by such hardware, hardware alone, or any combination thereof. The software may be stored on a program storage device readable by a machine.

In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable logic devices (FPLDs), including field programmable gate arrays (FPGAs) and complex programmable logic devices (CPLDs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.

In accordance with one embodiment of the present invention, the method may be implemented on a data processing computer such as a personal computer, workstation computer, mainframe computer, or high performance server running an OS such as Solaris® available from Sun Microsystems, Inc. of Santa Clara, Calif., Microsoft® Windows® XP and Windows® 2000, available form Microsoft Corporation of Redmond, Washington, or various versions of the Unix operating system such as Linux available from a number of vendors. The method may also be implemented on a multiple-processor system, or in a computing environment including various peripherals such as input devices, output devices, displays, pointing devices, memories, storage devices, media interfaces for transferring data to and from the processor(s), and the like. In addition, such a computer system or computing environment may be networked locally, or over the Internet.

In the context of the present invention, the term “network” comprises local area networks, wide area networks, the Internet, cable television systems, telephone systems, wireless telecommunications systems, fiber optic networks, ATM networks, frame relay networks, satellite communications systems, and the like. Such networks are well known in the art and consequently are not further described here.

FIG. 3 illustrates in schematic form the high level structure of a smart card 102 in accordance with one embodiment of the present invention. In the particular embodiments shown, the smart card is implemented using a Java Card system. Such a system is described for example in: “Java Card Technology for Smart Cards: Architecture and Programmer's Guide” by Zhiqun Chen, Addison-Wesley, 2000, ISBN 0201703297, while the formal Java Card specification is available for download from: http://java.sun.com/products/javacard/specs.html. Both of these texts are hereby incorporated by reference. Nevertheless, it will be appreciated that smart card 102 is not limited to the Java Card platform, and that alternative embodiments of the invention can be implemented on any suitable smart card platform.

Note that while smart card 102 is conveniently implemented in a plastic device similar in size and shape to a conventional credit card, in alternative embodiments it takes a variety of other portable formats, such as a ring, or a pendant, and so on. In other embodiments, smart card 102 comprises a token or similar device, such as for use in authentication. In addition, smart card 102 can be integrated into another electronic device. For example, in some embodiments smart card 102 comprises a Subscriber Identity Module (SIM) card for use in a GSM mobile telephone, or a Wireless Interface Module (WIM) for use in a device that supports the Wireless Application Protocol (WAP), or a Universal Subscriber Identity Module (USIM) card or a User Identity Module (UIM) for use in a 3rd Generation Partnership Project mobile telephone.

Smart card 102 can be regarded as having a layered structure, with hardware at the bottom. The hardware for a card comprises a CPU 311, a cryptographic facility 312, an input/output unit 313 and memory (random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM)) 314. Running on the hardware platform is a card executive layer 318, usually an operating system (OS) particular to the specific hardware platform involved. The card executive layer comprises an applet selector 412, whose operation will be described in more detail below.

On top of the card executive layer is the Java Card runtime environment (JCRE), which comprises the Java Card virtual machine (VM) 320. Note that the Java Card VM itself is generally specific to the particular card executive layer 318, but then presents the standard Java Card API 330 to application software 351 running on the smart card 102.

The Java Card device 102 depicted in FIG. 3 has (by way of example) five loaded applets 351A, 351B, 351C, 351D and 351E. Each applet 351 comprises a card AID interpreter 411, which will be described in more detail below. The applets 351A, 351B, 351C, 351D and 351E generally extend (i.e. subclass) a base applet class 321 provided by the JCRE 320. Similarly, the AID interpreters 411A, 411B, 411C, 411D and 411E extend a base AID interpreter class 322, which is also provided by the JCRE 320. Note that one or more of applets 351A, 351B, 351C, 351D and 351E may be from different vendors. It will be appreciated having multiple applications from different vendors installed on a single card avoids the need for a user to have to carry around multiple cards, one for each vendor or application provider.

The applets 351 are arranged into three groups, separated from another by firewalls 360. Thus applets 351A and 351B are in firewall 360K, applet 351C is in firewall 360L, and applets 351D and 351E are in firewall 360M. Applets 351 can share data within a firewall 360, but not generally from one firewall to another. One motivation for having two or more applets within a single firewall is where one applet manages the code and classes of the other application(s) that are within the same firewall. It is expected that all the applets within a particular firewall are controlled by the same RID operator (i.e. they have the same RID).

It will be appreciated that applets 351 are static, in that all the code they use is already stored in smart card 102. In other words, applications do not download any code from terminal 110 or elsewhere except during initial applet installation, at which time all the applet code is loaded for storage onto smart card 102 as part of the applet installation process.

In existing systems, it is difficult for external programs, such as may be running on a terminal 110, to ascertain and confirm the firewall structure of an inserted smart card. In other words, it is difficult for the terminal to deduce the allocation of applets 351 to firewalls 360, such as depicted in FIG. 3. Nevertheless, such information may be useful for the terminal in knowing how to handle the card in question, for example, because an applet can only access data within its own firewall. Furthermore, when an applet is first installed onto the card, it is clearly important to determine the correct firewall for the applet, so that the applet is installed into the proper location.

FIG. 4 depicts in schematic form the interaction between a smart card 102 and a terminal 110 in accordance with one embodiment of the invention. The smart card 102 comprises multiple applets, 351A, 351B, etc., each incorporating its own AID interpreter object, 411A, and 411B respectively. Each applet 351 also comprises its own AID 401. From a logical perspective, the AID 401 for a card can be regarded as contained with the card's AID interpreter 411. Thus a card AID interpreter 411 is responsible for providing access to the AID 401 (and parts thereof) for the applet 351 concerned. This interaction between the card AID interpreter 411 and the AID 401 is described in more detail below.

In operation, the smart card 102 contacts a terminal 110, which contains one or more proxies (410A, 410B). As shown in FIG. 4, there is a corresponding back office application 130A, 130B for each proxy. Note that in FIG. 4, there is a one-to-one correspondence between a proxy 410 in the terminal 110 and an applet 351 on smart card 102, although in other embodiments one proxy 410 may be associated with multiple applets 351. Each proxy comprises its own proxy AID interpreter 811 (again as described in more detail below).

If there is only a single proxy 410 installed on terminal 110, this can be set to trigger automatically when a card 102 is inserted into the terminal 110 (or otherwise engages with the terminal). Note that the proxy need not be terminated after each session with a card, but rather may only be suspended pending insertion of a new (potentially different) card. This helps to reduce proxy start-up time for the new card interacting with a terminal.

FIG. 5 illustrates the structure of an AID in terms of byte string 401 in accordance with one embodiment of the present invention. As previously described, an AID 401 is divided into two portions in accordance with the international standard ISO/IEEC 7816-5. In particular, the AID commences with a 5-byte RID portion 501 that identifies the supplier or operator of the applet 351 (i.e. the RID operator), and then has an 11-byte (maximum) proprietary application identifier extension (PIX) portion 502, whose format and content are under the control of the RID operator identified by the RID.

FIG. 5 further illustrates various subfields within the PIX portion 502 of the AID 401, in accordance with one embodiment of the present invention. Thus the PIX portion 502 is used to store both an identifier 502A of the firewall 360 that contains the applet concerned, and also an identifier 502B of the particular applet 351 itself. If required, additional information 502C can also be encoded into the PIX, as described later in more detail.

It will be appreciated that in contrast to the high-level breakdown of the AID 401 into RID and PIX portions, which is specified by the ISO7816-5 standard, there is no such standardization of the subfields within the PIX portion 502. Accordingly, the sizes and layout shown in FIG. 5 for the Firewall ID portion 502A, the Applet ID portion 502B, and the Other portion 502C are illustrative only, and may vary from one applet to another. For example, in one embodiment the bytes allocated to a particular subfield are not contiguous. Thus the Applet ID 502B can be stored in two separate blocks, with bytes indicative of the Firewall ID 502A located in-between. Furthermore, one or more of these subfields can be omitted altogether if not required by a particular RID operator. All such variations are of course still constrained by total size of the PIX 502, which is limited to 11 bytes (or at least no greater than 11 bytes), in conformity with the international ISO/IEC standard.

One motivation for storing the Firewall ID 502A within AID 401 is that although all applets in the same firewall are expected to relate to the same RID operator (i.e. have the same RID 501), the converse is not true. In other words, applets having the same RID may be located in different firewalls. This might arise if the cardholder has more than one relationship with an RID operator, and these different relationships are to be kept independent. One common situation in which this may occur is where an organization (such as a bank) is responsible for both a general card management application, and also some particular application for account manipulation, e.g. cash withdrawal from an ATM. In this case, the general card management application is likely to have privileges that should not be extended to the specific application for account manipulation. Another possibility is where a contractor for a large supermarket may have identity information encoded in a card to allow them to access particular areas of the supermarket in a business capacity. At the same time, the contractor may also have a loyalty or reward program installed in their card for when they make personal purchases at the supermarket.

FIGS. 5A, 5B, 5C, and 5D illustrate schemes for storing an AID byte string 401 within an applet 351 in accordance with alternative embodiments of the invention. In all cases the AID is accessed via the card AID interpreter object 411. The card AID interpreter object 411 supports a predetermined set of method calls to perform operations on the AID, such as (for example) get_AID( ), which accesses and returns the complete AID, get_RID( ), which accesses and returns just the RID component of the AID, etc. From the perspective of other software, the card AID interpreter 411 may therefore be regarded as an AID object. (Any separate existence of an AID object internal to the AID interpreter is transparent to software external to the AID interpreter).

The internal implementation of the card AD interpreter 411 differs between the various embodiments shown in FIGS. 5A, 5B, 5C, and 5D. However, it will be appreciated that these differences are transparent to (i.e. hidden from) software that uses the card AID interpreter 411 to access the AID and its components (due to object encapsulation). Thus in all cases there is a common method signature for the card AID interpreter class 411. Nevertheless, differences in the internal implementation of the card AID interpreter 411 may have implications for performance, required storage capacity, and so on, as will now be discussed.

In the embodiments illustrated by FIGS. 5A, 5B, 5C, and 5D, the underlying AID byte string 401 itself is stored in one or more byte arrays, although any other appropriate form of storage primitive(s) could be used. A byte array is then accessed via a buffer object 561, which is a general purpose object that provides method calls for accessing and manipulating its byte array of stored data (i.e. in this case the AID). However, the buffer object 561 has no knowledge of the internal composition of the stored data, such as that the first portion of the AID byte array represents the RID 501, and the second portion of the AID byte array represents the PIX 502.

In the embodiment of FIG. 5A, there is relatively little internal structure, and the card AID interpreter 411 calls the buffer object 561 directly in order to access the stored AID data. The card AID interpreter 411 therefore acts in effect as a wrapper for buffer object 561. In a variation on this configuration, the card AID interpreter 411 may be implemented as an extension of the buffer object 561. In either case, the AID interpreter 411 therefore has knowledge of the structure and coding of an AID 401, in order to be able to derive the various AID components from the full stored AID.

FIG. 5B illustrates an alternative implementation of the card AID interpreter 411, in which three components of the AID, namely RID 501, Firewall ID 502A, and the Applet ID 502B, are each represented by a respective (sub)object, namely RID object 540, Firewall ID object 541, and Applet ID object. These three subobjects interact with respective buffer objects 561A, 561B, 561C. (It is assumed here that the PIX portion comprises only a Firewall ID 502A and Applet ID 502B—i.e. that there is no Other portion 502C in this particular PIX 502). When card AID interpreter 411 receives a method call for the AID or one of its components, it calls the relevant subobject(s). For example, in response to a get_RID( ) call, the card AID interpreter 411 calls the RID (sub)object 540, while in response to a get_AID( ) call, the AID interpreter 411 retrieves all the components of the AID (i.e. RID 501, Firewall ID 502A etc.) from their respective subobjects 540, 541, etc. In the latter case, the card AID interpreter then knows how to assemble the retrieved AID components into the complete AID.

It will be noted therefore that the embodiment of FIG. 5B does not store the AID byte string as a complete entity per se. Rather, the various components of the AID are stored separately (in different byte arrays). These components are then assembled in response to a call into the AID interpreter to dynamically generate the complete AID. (A more extensive use of dynamically generated AIDs will be described later in more detail).

The embodiment of FIG. 5C represents something of a hybrid between the embodiments of FIGS. 5A and 5B. Thus in the embodiment of FIG. 5C, the AID subobjects (i.e. RID object 540, Firewall ID object 541, and Applet ID object 542) all access a single buffer object 561, which is used to store the complete AID. This use of a common buffer for holding the AID generally permits a more compact storage than the three separate buffers shown in FIG. 5B.

Note also that in the embodiment of FIG. 5C, the card AID interpreter 411 itself is also able to communicate with buffer 561 directly, i.e. not through one of the subobjects. This helps to speed up operations involving the whole AID (i.e. it avoids having to reconstruct the AID from its various components).

FIG. 5D illustrates another embodiment in which the Firewall ID object 541 and the Applet ID object 542 are implemented as transient objects (stored in RAM) rather than persistent objects (stored in EEPROM). In other words, the Firewall ID object 541 and the Applet ID object are only instantiated if particularly required, thereby saving storage on the card.

There are various trade-offs between speed, storage capacity, flexibility, and so on regarding the different embodiments of FIGS. 5A, 5B, 5C, and 5D. For example, the full subobject hierarchy of FIG. 5B provides a good logical representation of the AID structure, but may not offer the best performance levels.

Accordingly, it will be appreciated that the particular implementation adopted for card AID interpreter 411 in any given situation depends upon the circumstances in question. For example, one implementation may be selected if speed is of paramount concern compared to data and code storage capacity, while another embodiment may be selected if the relevant importance of performance and storage capacity is reversed. The skilled person will be aware of which embodiment to select for a given set of circumstances, and will also be aware of potential variations on the particular embodiments illustrated in FIGS. 5A, 5B, 5C, and 5D.

Returning now to the interaction between a smart card and a terminal, such as illustrated in FIG. 4, the provision of multiple (potentially unrelated) applications on a smart card makes it important that the correct application is selected and utilized for any particular session. Note that terminal 110 itself may be dedicated to a single type of application, or may instead support a range of applications.

In accordance with one embodiment of the invention, the interaction between a smart card and a terminal still follows in general terms the high-level pattern set out in FIG. 1B. However, at a more detailed level, the procedure is significantly different, as illustrated in FIG. 6, which depicts processing in accordance with one embodiment of the invention.

The processing of FIG. 6 commences with the receipt at 674 by the smart card 102 of a request from the terminal 110. This request generally corresponds to that transmitted at reference numeral 166 in FIG. 1B, except that the terminal 110 does not specify a single, complete (or partial) AID per se. Rather, the desired application is identified in terms of multiple parameters. These multiple parameters reflect the different components of the AID, for example as illustrated in FIG. 5.

It is now determined which application (if any) on the smart card is identified by the received parameters. This is achieved by comparing the received AID parameters against the AID parameters for the applications on the smart card, which as previously described can be accessed via the AID interpreter 411 for the corresponding applet. Accordingly, the AID interpreter 681 for each applet is located (681), thereby permitting the above comparison to be performed (693). Various mechanisms for performing this comparison are described in more detail below.

If the AID parameters from a particular applet match those received from the terminal (at reference numeral 694), then the complete AID is obtained from the relevant applet (696). This complete AID can then be returned to the terminal and the applet corresponding to the AID activated on the card (corresponding to reference numerals 177 and 179 in FIG. 1B).

If however the AID parameters from an applet on a card do not match those received from a terminal, then it is checked to see if there are any more applets to examine (695). If so, the AID parameters for these further applets are retrieved and tested against the AID parameters received from the terminal. However, if all the applets have now been tested without a positive response at 695, the smart card now reports to the terminal that it cannot find a match to the requested application (699).

FIG. 6A illustrates in more detail the processing of FIG. 6 in accordance with one particular embodiment of the invention. As previously described, this processing commences with the receipt at 674 by the smart card 102 of a request from the terminal 110. In this embodiment the desired application is identified in terms of three parameters:

-   -   (i) an RID 501     -   (ii) a firewall identifier 502A; and     -   (iii) an applet identifier 502B.         Note that although these parameters are logically separate, they         in practice be conjoined into a single string in the request         itself in order to facilitate transmission between the terminal         110 and the smart card 102 (this is discussed in more detail         below).

In one embodiment, if the firewall identifier 502A specifies a firewall that is known to contain at most only a single application, then the applet identifier 502 can be omitted. Conversely, the firewall identifier 502A can be omitted in one embodiment, for example if the applet identifier 502B is known to be unique to that RID 501.

A request containing the above three parameters is therefore received on the smart card at 674 by the applet selector 412 (see FIGS. 3 and 4). The applet selector then has to find an application 351 on the card that matches these parameters (corresponding in general terms to reference numeral 176 of FIG. 1B, or to reference numerals 681, 682, and 684 of FIG. 6). Thus following receipt from terminal 110 of the request specifying the RID 501, Firewall ID 502A, and Applet ID 502B of the desired applet, the applet selector 412 calls each installed applet to try to match these three parameters. More particularly, a first applet is selected (680), and the applet selector 412 calls this applet in order to obtain access to the card AID interpreter 411 within the applet (681).

Once the card AID interpreter for the applet has been located, the applet selector 412 calls a match_RID( ) method (or such-like) on the card AID interpreter 411 (682). In making the match_RID( ) call, the applet selector passes as a parameter the particular RID 501 that was received from the terminal—i.e. the RID to be matched. The card AID interpreter 411 then tests the received RID against the locally stored RID for that applet (684). The exact manner of performing this test will depend upon the method signature and internal implementation of the card AID interpreter 411, such as discussed above in relation to FIGS. 5A, 5B, 5C, and 5D.

After the card AID interpreter 411 has tested the RID received from the terminal against the RID for that applet, the match_RID( ) method call returns a positive or negative response as appropriate (684). If this response is negative, then it is known that this applet cannot be the one desired by the terminal 110, since the RID does not match. Accordingly, in this case the applet selector 412 proceeds to select another applet 351 on the card to test (697).

On the other hand, if an RID match is obtained at 684, the applet selector 412 next examines whether the Firewall ID received from the terminal matches the locally stored Firewall ID for the applet. This testing is again performed by making an appropriate call (e.g. match_FirewallID( )) from the applet selector to the card AID interpreter 411 (686). If the card AID interpreter produces a negative response to the match_FirewallID( ) call, the Firewall ID received from the terminal does not match the Firewall ID stored in the applet. Accordingly, the applet in question cannot be the one desired by the terminal. The applet selector therefore again proceeds to select the next applet for investigation (697).

Alternatively, if the testing of the Firewall ID at 688 results in a positive match, the applet selector 412 now examines whether the Applet ID received from the terminal matches the Applet ID stored within this applet (690). Again, this is achieved by making an appropriate method call into the card AID interpreter 411 (690). In response to this call, the card AID interpreter 411 tests the Applet ID received from the terminal against the Applet ID stored within the applet (692). If this test yields a negative outcome, then the applet in question cannot be the one desired by the terminal, since the Applet ID does not match. Accordingly, the applet selector 412 again proceeds to select the next applet for consideration (697).

On the other hand, if the test of Applet ID at 692 gives a positive result, then the desired applet been located, since the RID, Firewall ID and Applet ID must all match. In this case, the applet selector 412 calls the get_AID( ) method of the card AID interpreter 411. This call returns the complete AID for the matching applet (696), which can then be passed back to the requesting terminal (corresponding to reference numeral 179 in FIG. 1B). In addition, the matching applet will also be launched on card 102 (corresponding to reference numeral 177 in FIG. 1B).

Note that it has been assumed so far that there is a single applet 351 on a card that matches the terminal request. However, this assumption may not necessarily hold. Thus if the application 351 requested by the terminal 110 is not present on the card 102, then no matching applets will be found. This situation is accommodated in the flowchart of FIG. 6A where a test is made at 695 to see if all the applets have been examined. If so, and there are no further applets to investigate on the card, the applet selector 412 has to send a negative report back to the terminal (699), indicating that the requested application is not installed on the card. Depending on the particular terminal in question, this may terminate the session between the card and the terminal, or may lead the terminal to submit a request for a different application on the card (i.e. to specify a different set of RID 501, Firewall ID 502A, and Applet ID 502B parameters).

It is generally expected that the RID, Firewall ID and Applet ID reliably define a unique application, so that the situation of finding more than one matching applet on a card for a particular terminal request should not arise. However, in some embodiment, a more generic matching process can be utilized. For example, the terminal can be permitted to omit an applet ID from its request at 674. In this case, there may potentially be multiple matching applications (i.e. all the applications located within the specified firewall). One option would be to handle this situation similarly to the way in which existing systems handle a partial AID that matches multiple applications (i.e. by returning one match at a time for each terminal request). Another possibility is to modify the flowchart of FIG. 6A by proceeding from 694 (obtain whole AID) to 695. In this case, processing would always eventually arrive at 699, once the applet selector had investigated all the applets on the card. At this point the applet selector 412 can then return to the terminal the complete set of matching AID(s) that have been found, or report the absence of any match (as appropriate).

FIG. 6B depicts an alternative implementation of the application matching process in accordance with one embodiment of the invention. Note that many aspects of this embodiment are the same as for the embodiment of FIG. 6A, and so will not be described in detail. The main difference is that in this implementation it is the applet selector 412 that is responsible for performing the testing of the three input parameters, namely the RID 501, the Firewall ID 502A, and the Applet ID 502B (rather than the card AID interpreter 411, as in the embodiment of FIG. 6A).

The processing of FIG. 6B again starts when a terminal 110 sends a request containing the parameters identifying the desired application, and this request is then received by the smart card (674). However, instead of the applet selector 412 now passing these parameters to the selected individual applets 351 (as in the embodiment of FIG. 6A), in this embodiment the applet selector 412 calls the card AID interpreter 411 for each selected applet in order to retrieve the corresponding parameters stored in that applet. Thus the applet selector retrieves the RID 501 for a selected applet from the card AID interpreter 411 at 682B, the Firewall ID 502A for the selected applet from card AID interpreter 411 at 686B, and the Applet ID 502B for the selected applet from card AID interpreter 411 at 690B. The retrieval of 682B can be regarded as being performed using a get_RID( ) call, in contrast to the match_RID( ) call used in the embodiment of FIG. 6A.

After each parameter has been retrieved from the card AID interpreter 411, the Applet selector 412 tests the retrieved parameter against the corresponding parameter received in the request from the terminal. Thus applet selector 412 tests at 684 for a match of RID 501, at 688 for a match of Firewall ID 502A, and at 692 for a match of Applet ID 502B. If all three matches turn out positive, then the desired applet has been identified, and the applet selector can request the complete AID for this applet from the relevant card AID interpreter (694). (Note that the applet selector 412 itself will not generally know how to form a complete AID from the three parameters it already has, nor will it know whether any additional information, such as Other 502C (see FIG. 5), might be required for such a task). The applet selector can then return the complete AID back to the terminal that originally submitted the request (corresponding to reference numeral 179 in FIG. 1).

It will be appreciated that there are many variations on the above approach. For example, rather than investigating the RID, the Firewall ID, and the Applet ID in turn, the card AID interpreter 411 can support a single combined method call to match (or retrieve) two or three of these identifiers at once. One example of this is shown in FIG. 6C, which depicts processing in accordance with one embodiment of the invention. The flowchart of FIG. 6C is broadly similar to the flowchart of FIG. 6B, except that the applet selector retrieves all three parameters, namely the RID, the Firewall ID and the Applet ID, in a single operation at 682C. These three retrieved parameters can then be matched against the parameters received from the terminal, in the same way as described for FIG. 6B. Note that in one embodiment, the selector can retrieve the complete AID at 682C as well as the various AID components, in which case reference numeral 696 of FIG. 6C can subsequently be omitted.

FIG. 6D illustrates a further embodiment, which is the same as that of FIG. 6C, except that the parameter matching is performed by the various AID interpreters 411 at 682D (as in FIG. 6A), rather than by the applet selector. Thus in the embodiment of FIG. 6D, the applet selector 412 invoke a (combined) call on the AID interpreter 411, and as part of this call passes to the card AID interpreter 411 of an applet the parameter triplet of RID 501, Firewall ID 502A and Applet ID 502B received from the terminal (682D). The card AID interpreter 411 then tests these three parameters against the corresponding components of the AID stored within the relevant applet (reference numerals 684, 688, and 692). If all three parameters match, then the card AID interpreter 411 returns a positive response to the call. On the other hand, if one or more of the parameters do not match, a negative response is returned. (N.B. In one implementation, in the event of all three parameters matching, the card AID interpreter 411 comprises the complete AID string in its return to the applet selector 412, thereby avoiding the applet selector having to make a separate request for this at 696).

A further possible variation is that rather than the applet selector investigating the different applets on a card sequentially (i.e. one applet at a time), as in FIG. 6, the applet selector 412 instead investigates multiple (potentially all) applets at the same time. In other words, the processing of FIG. 6 (reference numerals 681 through to 694 in particular) is performed for each applet in parallel. This is illustrated in the flowchart of FIG. 6E, which depicts processing in accordance with one embodiment of the invention. Note that the processing of FIG. 6E can be performed by any suitable parallel implementation of the flowcharts of FIGS. 6A through 6D, in which case the loop back via reference numeral 697 is clearly omitted. The applet selector 412 can then collate the results from each separate applet in order to determine overall whether a matching applet has been identified.

Although the embodiments of FIGS. 6 through to 6E all perform the applet matching on the smart card 102, this matching can also be performed on terminal 110, as illustrated in the flowchart of FIG. 6F, which depicts processing in accordance with another embodiment of the invention. The flowchart of FIG. 6F commences with the terminal requesting information about the applets on the card 102 (604). In response, the terminal receives the RID 501, firewall ID 502A and applet ID 502B as well as the complete AID 401 for each applet on the card (606). This allows the terminal to try to identify the desired applet, based on matching its RID 501, firewall ID 502A and applet ID 502B (610). Once this applet has been identified, the terminal can now ask the applet selector 412 to launch or activate this applet by specifying the corresponding (complete) AID (612). A further possibility is for the terminal itself to comprise a proxy AID interpreter 811, as described in more detail below.

It will be appreciated that selecting an application on the basis of the RID 501, Firewall ID 502A, and Applet ID 502B avoids a terminal 110 having to identify a desired application by its precise AID 401. This considerably enhances flexibility compared to existing implementations, in which a terminal has to provide a full or partial AID, and receives back the full AID for each matching application. In particular, it is now possible for the contents and format of an AID 401 to vary without compromising compatibility with the terminal 110, provided that the Firewall ID 502A and Applet ID 502B themselves are maintained constant.

There are several reasons why such variation in the contents and structure of an AID 401 may occur. For example, the PIX portion 502 of the AID can be used to store additional information (i.e. Other 502C, as shown in FIG. 5) which is potentially variable. Such additional information can relate to the card itself, such as its remaining memory capacity. Another possibility is that this additional information relates to the card application corresponding to the AID in question. For example, the Other 502C portion can comprise a version number or configuration details for the application. According to one embodiment, the information in the Other 502C portion is used for application selection. According to another embodiment, the information in the Other 502C portion is used for further processing of the session.

The additional information stored in the Other 502C is normally not available to the terminal 110 (prior to interaction with card 102). Consequently, the terminal does not know the entire AID for matching. However, using an approach such as illustrated in FIGS. 6 though 6F, the terminal can still locate the desired application on the card by virtue of the application's RID, Firewall ID, and Applet ID, which the terminal does know in advance.

Of course, existing systems can potentially accommodate additional (variable) information in the AID by placing such information at the end of the AID, and then using a partial match on the prior (fixed) portion of the AID. However, this requires the terminal to know in advance the specific byte sequence for the partial AID. Furthermore, it also restricts the placement of any variable information to the end of the AID. In contrast, the approach described herein does not impose any restrictions as to where or how the Firewall ID 502A and the Applet ID 502B are stored within the PIX portion 502 of the AID. For example, they could be located at the end of the AID, after any other (potentially variable) information.

In one embodiment, the terminal and the AID interpreter apply a shared or common data representation to the Firewall ID and the Applet ID. This common data representation can correspond to a primitive data type (such as an integer), or to a complex data type (such as a 16-byte string). This shared representation is generally larger than the actual number of bytes allocated to each parameter inside the stored AID (which is of course limited to a maximum of 11 bytes corresponding to the size of the PIX portion 502 of the AID). Consequently, the AID interpreter 411 performs the appropriate size conversion between the internally stored Firewall ID (of say 3 bytes) and the external data representation of the Firewall ID (of say 16 bytes), and vice versa, as required.

Having a shared data representation for external manipulation of the Firewall ID 502A and/or Applet ID 502B portions allows the internal storage of these parameters to be altered without impacting terminal compatibility. For example, a particular supplier (i.e. having a particular RID 501) may have originally allocated a certain portion of the PIX 502 to the Firewall ID 502A and the remainder to the Applet ID 502B. However, it may subsequently transpire that there are a greater number of potential Firewall IDs than can be accommodated within the initially allocated portion. In this situation, the supplier may decide to increase the portion of the PIX 502 used to store the Firewall ID 502B. Since terminal 110 is only concerned with the external manifestation of these parameters, such modifications are quite transparent to the terminal. (In contrast, if the terminal 110 were matching a precise AID string, as in existing systems, the byte reallocation between the Firewall ID and the Applet ID is potentially problematic).

A further possibility is to divide the PIX portion at the bit (rather than byte) level, which helps to maximize utilization of this very limited coding space—e.g. a single byte can be split across two or more fields. This then requires somewhat more complicated processing of the internal representation (i.e. within the AID interpreter), given the need to work with individual bits. However, if the common data representation is maintained at the byte level, external programs (such as running on terminal 110) are shielded from the complexities of the internal bit operations.

It will be appreciated that if the internal data format within the AID interpreter is different from the common data representation, then operations involving getting (reading) or matching an AID component have to perform a conversion from internal to external format. The conversions for such reading or matching operations can be achieved in a straightforward manner by prepending the appropriate number of null bytes (e.g. 13 in the above case) in order to convert from an internal format into an external format.

Note that the situation is a little more complex in reverse, when going from the external representation to the internal representation. In these circumstances, the value supplied from the terminal will generally be longer (say 16 bytes) than the space available (say 3 bytes) within the AID byte array on the card (or other internal storage facility). If most of the bytes in the AID parameter passed from the terminal to the card are zero, they can be truncated to fit the parameter into the AID byte array. On the other hand, if a non-zero byte is to be truncated, then this generally represents an error situation, and should be flagged accordingly. However, the AID components in question (i.e. the Firewall ID portion 502A and the Applet ID portion 502B) are not normally updated after applet initialization, thereby avoiding difficulty in this respect.

In summary therefore, the present approach matches AID parameters (generally RID 501, Firewall ID 502A and Applet ID 502B) via an AID interpreter in order to identify a desired application on a card. The precise manner in which the AID and its components are encoded and stored onto card 102 is hidden behind the AID interpreter, and need not be known to the terminal 110. This then enables terminal 110 to use a relatively stable and straightforward interface to identify applications across a wide range of cards 102, preserving compatibility without unnecessarily constraining the contents of the AID itself. Consequently, the extra level of indirection, whereby the AID 401 contents are only accessed via AID interpreter 411, provides great flexibility as to how the AID 401 is utilized and updated.

Note that although FIGS. 6 through 6F depict from the handling of an AID in terms of multiple (logical) components, it will be appreciated that from an implementation perspective the separation of these parameters can be less apparent. For example, in communications between the smart card 102 and the terminal 110, the parameters (i.e. RID 501, Firewall ID 502A and Applet ID 502B) can be combined into a single byte sequence for ease of transport and manipulation (e.g. as a data packet). This implies that in addition to a single common data representation for the parameters themselves, there can be a standard way of packing them into a single byte sequence or other appropriate transport format.

Likewise, although the different parameters are depicted in FIG. 5 as independent of one another, this need not necessarily be the case. For example, in some embodiments the firewall ID can in fact be defined as the concatenation of RID portion 501 and Firewall ID portion 502A. It will be appreciated that such an approach still allows a terminal or other software to distinguish between applications in different firewalls. Moreover, this hierarchy reflects the fact that each RID operator (as defined by RID 501) defines its own set of firewalls, and so Firewall ID portion 502A can only be sensibly interpreted given its corresponding RID portion 501. An example of an implementation that adopts such a hierarchical structure is included in Appendix A.

FIG. 7 is a flowchart that illustrates in more detail a mechanism for a card AID interpreter 411 to provide an AID in accordance within one embodiment of the invention. The processing of FIG. 7 illustrates in particular the situation where at least a portion of the AID is constructed dynamically using state information maintained on the card 102. In other words, the AID is used to encode information about the state of the card or the application corresponding to that AID. Some of this data may be stored separately from the static portions of the AID (such as RID 501, Firewall ID 502A, and Applet ID 502B0). This state information then has to be dynamically combined with the static portions to create the complete AID. (N.B The Other portion 502C of an AID, such as illustrated in FIG. 5, may comprise static data and/or dynamic data).

The flowchart of FIG. 7 commences with the card AID interpreter 411 receiving a method call for the (complete) AID (710). Such a call can arise during a session with a terminal, perhaps because the applet selector 412 wants to retrieve the AID for the matching application in order to return the AID to the terminal (as per reference numeral 696 of FIG. 6). However, the card AID interpreter may have to provide a complete AID in other circumstances as well. One possibility is that a smart card is asked to provide a complete listing of AIDs for the applets installed on the card, either for applet selection purposes (as in FIGS. 6 and 6A), or for more general card management operations. Another possibility is that if a transaction updates some portion of the AID to be stored on the card, then it can request a read-out of the AID at the end of the session, in order to confirm that the update has been correctly saved onto the card.

The AID interpreter responds to the request of reference numeral 710 by accessing the stored AID byte array (720). The exact manner in which this is performed depends on the internal implementation of the AID interpreter, as discussed above in relation to FIGS. 5A, 5B, 5C, and 5D. For some applets, the byte array retrieved at this stage represents the complete AID (i.e. there is a negative outcome to the test of reference numeral 730). In such cases, the card AID interpreter can immediately proceed to return the retrieved AID to the calling object (reference numeral 770, via reference numeral 730). However, in other situations, the AID comprises a dynamic component, i.e. there is a positive outcome from reference numeral 730. (It will be appreciated that in an actual implementation of a card AID interpreter 411, the test of reference numeral 730 may be omitted; rather, the card AID interpreter is hard-wired to include, or not to include, dynamic data, as appropriate for the applet in question).

The dynamic component of the AID may represent, for example, a current balance for the card, the date of the last transaction of an application, or any other desired data. This dynamic data can, in principle, be stored within the card AID interpreter 411 itself, and so be directly accessible to the card AID interpreter. However, more generally the dynamic data is located separately from the card AID interpreter, which pulls in the dynamic data on-the-fly when it is required to generate a complete AID. For example, in some embodiments the dynamic data is held in general card data storage 414 (see FIG. 4), which can be implemented in a portion of EEPROM 314 assigned to or accessible by the application in question.

If the AID does incorporate dynamic data, the next task is to assemble the complete AID from this dynamic data and the static data (735). The exact manner of doing this depends upon how and where the dynamic data is stored. FIG. 7 illustrates one particular situation, where the card AID interpreter 411 calls the applet to which the card AID interpreter belongs to provide the dynamic data (740). The applet responds by obtaining the dynamic data, for example by accessing one or more subobjects within the applet that are responsible for maintaining the dynamic data. Next, the applet returns this dynamic data to the card AID interpreter, for example by using a call-back mechanism (750). When the AID interpreter 411 has obtained the desired information, it generates a composite or final AID by combining the stored and dynamic components as appropriate (760). The newly generated AID can then be returned (770) in response to the original request at reference numeral 710.

It will be appreciated that there are many other possible implementations of reference numeral 735 apart from that shown in FIG. 7. For example, in some embodiments the card AID interpreter itself maintains the dynamic AID component, in which case it would not need to contact the applet for this information. Alternatively, the applet may (upon prompting) write the dynamic component directly into the low-level AID storage facility. In this situation, reference numeral 720 is postponed until after 735, whereupon the card AID interpreter 411 would, in effect, retrieve a complete and already updated AID. Other possible implementations will be apparent to the skilled person.

An example of the dynamic data that can be handled by the processing of FIG. 7 is a credit balance controlled by a purse object. The purse object may perhaps store two parameters in card data 414, the first representing the amount of money deposited onto the card, and the second the amount of money spent from the card. The difference between these two amounts then gives the current balance, and it may be this figure (the balance) that is to be incorporated into the AID. In this situation, the purse object responds to the call of reference numeral 740 by calculating the current balance (i.e. by subtracting the amount spent from the amount deposited), and then returning the balance to the card AID interpreter for incorporation into the AID. Note that in this implementation, not only is the AID assembled dynamically, but it also incorporates data that does not normally exist per se on the card (rather, the dynamic data that is incorporated into the AID is derived from other data values that are present on the card).

It will be appreciated that there is a wide range of possibilities for dynamic data to be included in an AID. For example, the dynamic data can reflect the date and/or time of last use of the application, the location of the terminal of last use, or any other desired application or card property. This then gives considerable flexibility in terms of how the card, and in particular the AID, is used.

Note that the dynamically inserted data is not necessarily subject to change during the lifetime of the card or application. In some embodiments this data can instead represent a fixed (or relatively fixed) property, such as the remaining memory capacity of the card, the version number of an applet, etc. One advantage of storing details of this (potentially fixed) property or state outside the card AID interpreter 411 is where the same data is to be utilized by multiple applications. For example, the AID may be constructed to comprise an indication of which encryption facilities are present on the card, since this may impact the type of operations that a terminal can perform with the card. However, since these encryption facilities are common to all applications on the card, it is convenient for the relevant indication to be stored in a single, centralized location (such as in card data 414).

In these circumstances, the card AID interpreters for the various applications on the card 102 can use the procedure of FIG. 7 to retrieve this centralized indication of encryption facilities as dynamic state information. The retrieved information can then be incorporated into the AID for the respective applications, as and when required by the AID interpreters 411. It will be appreciated that storing a single copy of data (in this case the indication of encryption facilities) in a shared resource, such as data block 414, where it can then be accessed by multiple applications on the card, is generally more efficient than encoding the data separately into the AID for each application on the card.

Another benefit of storing dynamic data outside the card AID interpreter 411 is that the card AID interpreter itself does not need to know how to access, manipulate or format the dynamic data. Rather, this can be left to those objects that primarily interact with the dynamic data (and possibly update it). This then allows a higher degree of generality for the card AID interpreter 411 itself.

Thus in one embodiment the card AID interpreter knows whether or not the AID comprises dynamic data, and if there is such dynamic data, how to obtain it (e.g. which method to call on the applet) and how to incorporate it into the AID byte string (perhaps to insert the dynamic data as Other 502C in bytes 13-15). However, the card AID interpreter does not need to have any further understanding of or interaction with the dynamic data.

For example, if the smart card stores two values, one representing amount placed on the card, the other amount spent (as suggested above), then in general the card AID interpreter 411 does not calculate the balance itself. Rather, the card AID interpreter calls its applet for the dynamic data to incorporate into the AID, and receives back the balance (already calculated) in response. The applet itself can obtain the balance by calling an appropriate method on the object responsible for maintaining the two data values in question (such as a purse object). This object then performs the necessary subtraction in order to produce and return the current balance to the card AID interpreter. The same object would also generally be responsible for suitably formatting the dynamic data for inclusion in the AID. For example, where the balance details are maintained in the purse object as real numbers (or possibly integers), the result can be converted into a byte string before return to the card AID interpreter for compatibility with the rest of the AID.

As described above, the presence of the AID interpreter 411 on smart card 102 relieves the terminal 110 of having to utilize the AID 401 directly in order to locate a desired application. Nevertheless there are other situations where the terminal 110 itself does want to be able to access and interpret the AID 401. For example, there may be other information encoded into an AID 401 passed to the terminal 110 that the terminal desires to use during the session, such as the Other portion 502C (see FIG. 5).

This situation is addressed by the procedure of FIG. 8. FIG. 8 which illustrates processing performed at a terminal 110 during a session with a smart card 102 after preliminary interactions between the terminal 110 and the card 102, such as card activation (see FIG. 1B), have been completed, in accordance with one embodiment of the invention. The flowchart of FIG. 8 commences with the terminal specifying a desired matching application (8005). This operation corresponds in general terms to reference numeral 166 of FIGS. 1B and 1C. In the particular implementation shown, the request for a matching application is performed using multiple parameters, such as RID 501, Firewall ID 502A, and Applet ID 502B. These parameters allow the smart card to identify a matching application, as described above in relation to FIGS. 6 through 6E. The smart card then returns the AID for the matching application, which is duly received by the terminal (reference numeral 8010, see also reference numeral 180 of FIGS. 1B and 1C).

Having received the AID from the card, the terminal has to interpret the AID in order to complete the desired user interaction. However, maintaining knowledge of the AID structure within the terminal itself can be problematic, particularly where the terminal 110 supports multiple applications from a variety of suppliers. Furthermore, as described above, a matching application can now be identified on the basis of certain parameters, such as Firewall ID and Applet ID, rather than requiring the terminal to store a complete AID string for this purpose. Having therefore avoided the terminal initially needing full knowledge of the AID on the card for application selection, it is also desirable to prevent the terminal having to maintain a detailed understanding of the AID format for subsequent interaction with the application. This then allows a terminal to be generic as possible, and avoids having to update terminal software whenever there is a change in AID structure (or conversely, permits changes in AID structure without compromising compatibility with the installed base of terminals).

Nevertheless, a terminal always knows from international standard ISO/IEC 7816-5 that the first five bytes of an AID represent the associated RID 501. Accordingly, once the terminal has received the incoming AID from the smart card 102, it is able to retrieve this RID portion 501 by extracting the first five bytes of the received AID (8020).

In accordance with the procedure of FIG. 8, the terminal now uses this RID portion 501 to obtain some form of network resource identifier (8030). This network resource identifier represents a Uniform Resource Locator (URL) on the Internet (or similar intranet or extranet). Alternatively, it may represent any other suitable type of network address or resource specifier, etc. There are a variety of possible mechanisms by which such a URL may be acquired from the extracted RID portion 501. For example, the terminal may maintain a lookup table that maps from RID portion 501 to specific URL. Alternatively, the terminal may follow some algorithm to convert from the RID to a URL. A further possibility is that some hybrid of the above two approaches is adopted, such as using the lookup table as the first option, and then forming a URL directly if there is no entry in the lookup table for that particular RID.

If reference numeral 8030 involves forming a URL directly from the RID, then some mechanism is provided (such as a constructor method) for converting from the RID byte string into a URL. Thus the RID byte string can first be represented in hexadecimal form, which is then transformed into a corresponding text string for incorporation into a URL. Alternative methods for deriving a network resource identifier from the RID byte sequence can also be employed, such as using one or more bytes directly to specify an IP address of a URL (this can be done by using the “%” character, followed by two hexadecimal characters to specify an octet).

Note that any initial mapping of the AID into a URL by the terminal is non-semantic, in that the terminal converts the AID byte sequence into a URL via some mechanism such as the hexadecimal transformation discussed earlier. However, this mapping process is not expected to recognize or interpret any components of the AID (other than perhaps the RID, whose position within the AID is predefined by standard).

Once the network resource identifier has been derived from the RID, terminal 110 now sends a request to the URL or other address corresponding to the RID 501 (8040). In due course, the terminal receives back over the network a response comprising some form of material relevant to the AID (8050), which is then used to support further activities in the session (8060). It will be appreciated that the manner of this use depends upon the nature of the downloaded material (e.g. whether it is code, data or a network service address, etc.). One particular situation, where the downloaded material comprises an AID interpreter for use on the terminal 110, will be discussed in more detail below.

Returning to reference numeral 8030, the RID can be used to define the domain name portion of a URL. In other embodiments, the RID can be provided in effect as an http parameter associated with the domain. One embodiment involving the former option is illustrated in FIG. 8A, which provides more detail for FIG. 8. Thus in FIG. 8A, the network resource identifier represents a URL which is derived from the RID by performing a lookup in a table or database, etc. (reference numeral 8030A, corresponding to reference numeral 8030 in FIG. 8). The table or database is maintained locally on the terminal. The terminal then downloads code and/or data as required from this URL (reference numeral 8040A, which can be regarded as corresponding to both reference numerals 8040 and 8050 in FIG. 8).

In some embodiments, the URL initially derived from the RID 501 comprises a guide or indicator to one or more sites from which further material can be accessed. For example, the URL initially obtained at 8030 can provide a link to a further web site where the material is located (perhaps using the http redirect mechanism). The terminal then follows this link (or chain of links) in order to retrieve the relevant material. An example of this is where the terminal forms a URL comprising a generic portion, representing perhaps a constant Web site (and page), and an RID-dependent portion, comprising the RID in hexadecimal form. The RID-dependent portion is therefore presented in effect as an entry field associated with the generic page (analogous to encoding a search term into a URL for a search engine). This can then be used to determine the address of further material.

Such an embodiment is illustrated in the flowchart of FIG. 8B, which again provides more detail for FIG. 8. Thus in FIG. 8B, the RID received from the card is appended as a search parameter to a predetermined first URL stored locally on the terminal (reference numeral 8030B, corresponding to reference numeral 8030 in FIG. 8). This then forms a search request which is sent to the first URL (reference numeral 8040B, corresponding to reference numeral 8040 in FIG. 8). In response to this request, the terminal receives a second URL (reference numeral 8050A, corresponding to reference numeral 8050 in FIG. 8). The terminal now downloads code and/or data from this second URL for use in the session with the card (reference numeral 8060B, corresponding to reference numeral 8060 in FIG. 8).

There is a very wide range of material that can potentially be obtained by the terminal at reference numeral 8050 in FIG. 8. For example, in the embodiment of FIG. 8B, the material initially downloaded for use in the session is in fact the second URL, which then directs the terminal to another location from which additional material can be obtained. In another embodiment illustrated in FIG. 8C, the downloaded material comprises a data mapping, representing the structure of the AID 401 used by that organization (reference numeral 8050C, corresponding to reference numeral 8050 in FIG. 8). The terminal can then use this mapping in order to extract desired information (such as a current balance) from the AID supplied from the smart card (reference numeral 8060C, corresponding to reference numeral 8060 in FIG. 8). Note that there can be multiple such mappings for a single organization (as specified by the RID), with the particular mapping to be used dependent on some other data encoded into the PIX portion of the AID. In one such embodiment, the terminal receives over the network a full set of possible mappings for that RID, and then selects an appropriate mapping from this set based on the particular AID that it obtained from the smart card. In another embodiment, illustrated in FIG. 8D, the terminal incorporates the full AID into the initial network request of reference numeral 8040D (corresponding to reference numeral 8040 in FIG. 8). The web server receives this request (8043) and uses the complete AID to select the material to supply back to the terminal (reference numeral 8046), downloading only the material (e.g. a mapping) appropriate to that particular AID (8049), which is received by the terminal in due course (reference numeral 8050D, corresponding to reference numeral 8050 of FIG. 8).

In other embodiments, the material received by the terminal over the network comprises code (potentially in addition to other forms of material). There are a variety of possible code components in the supplied material, such as a user interface for the terminal to use with the cardholder, or a proxy AID interpreter 811 (see FIG. 4) to allow the terminal 110 to decode the AID received from the smart card. In an alternative embodiment, the code downloaded is responsible for actual processing of application data during the session with the card (i.e. forming part of proxy code 410). It will be appreciated that two or more of these code components can be downloaded in any given session.

The code can be provided to the terminal in a variety of forms, such as raw class files or as Java Archive (JAR) files or packages, each containing (compressed) Java code plus manifest. The downloaded code can then indicate further classes or packages that may need to be retrieved from over the network in order for the application to run. A further possibility is that the terminal receives a Java Application Descriptor (JAD) file. This is an XML file that comprises one or more URLs specifying where the relevant application code is located, as well as the location of any data associated with the application. The XML file can further comprise one or more descriptors relating to the application. The terminal can then download the code and data in accordance with the information provided in the JAD file.

Other types of material that can be downloaded over the network in response to the request from the terminal include multimedia data, such as a logo image to be utilized for the user session on a terminal screen; some form of contractual documentation associated with the session—perhaps a user license or agreement; and some form of authorization or verification, such as a third party certificate guaranteeing the bona fide nature of a merchant involved with the session.

The material can also comprise a further network resource identifier representing a location, such as a portal, where a desired service can be obtained. Such a service may be the download of some product (e.g. music), some on-line purchase facility (e.g. for buying aircraft tickets), some data service (e.g. the supply of recent financial results), and so on. This further network resource identifier can also represent a site at which documentation relating to the commercial transaction (such as contractual details) is located. It will be appreciated that in many circumstances, the terminal is specialized for a particular application—e.g. the terminal may comprise a facility to print aircraft tickets, or to burn music downloaded from the network onto a customer CD. The nature of the terminal will then determine the range and nature of application processing available to a customer at the terminal.

Note that the terminal can download multiple different items for a single smart card session. For example, from the initially derived network resource identifier (at reference numeral 8030), the terminal may obtain a set of further URLs specifying locations of various types of material relevant to the session (code, contractual terms, payment service location, etc).

It will also be appreciated that in some situations certain material available from a URL may in fact already be present on the terminal. For example, some Java packages from a specified URL may have previously been downloaded (for example as JAR files) and installed onto the terminal, perhaps to process an earlier session with a different card. In these circumstances, it will not normally be necessary to repeat the download (unless perhaps an expiry date for the material has passed). More generally, the terminal may already have available the material corresponding to the network resource identifier generated at 8030, either because the material is cached or mirrored locally, or because the identified resource happens to be located on the terminal itself. The material can then be accessed locally at reference numerals 8040 and 8050 without having to download over the network.

FIG. 8E illustrates a flowchart for one embodiment of the invention that takes into account the possibility of the terminal already having the specified material. Thus as shown in FIG. 8E, a test is made at reference numeral 8033E to determine whether or not the terminal already has material from the relevant network address. If so, this material can be used directly by the terminal, without having to be downloaded over the network. (The remainder of the processing of FIG. 8E is the same as that for FIG. 8).

As mentioned above, the terminal can use more than just the RID portion 501 of the AID in the processing of FIG. 8. For example, if the network resource identifier is generated at 8030 by having the RID as an entry field or input parameter for a URL request, then the PIX portion can be provided likewise as an input parameter in the URL request. The web server can then utilize the PIX portion in determining the response that is provided back to the terminal (see reference numeral 8046 of FIG. 8D). For example, the web server may determine the type of application associated with the AID (based perhaps on the Applet ID in the PIX portion), and then provide code back to the terminal that is appropriate for interacting with this particular application.

In some embodiments, the web-site or other network location performs some semantic interpretation of the AID obtained from the smart card by the terminal, so that the response back to the terminal incorporates data extracted from the AID (such as a current balance on the card, or other such state information included in the AID). This provides one mechanism to avoid the terminal itself having to be able to decode or interpret the AID byte string. Such an embodiment is illustrated in the flowchart of FIG. 8F, which generally corresponds to that of FIG. 8D, except that at 8046F, the server interprets the received AID in order to extract relevant information. This extracted information can then be returned to the terminal (8049F) for further processing in the session.

Note that the processing of FIG. 8 following reference numeral 8010 (receipt of the AID from the smart card 102) is generally independent of the exact mechanism or circumstances whereby this AID is obtained. For example, the AID may be received following the operations described in relation to FIGS. 1B or 1C (i.e. without the use of multiple parameters to specify a matching application on the smart card). In addition, the processing of FIG. 8 (from reference numeral 8010 onwards) might also be performed if a terminal receives an AID from a smart card not as part of the initial selection of a matching application, but rather at some subsequent stage of the session between the card 102 and the terminal 110.

FIG. 9 depicts in more detail the server processing in response to the (http) request of reference numeral 8040 of FIG. 8 for one particular embodiment of the invention. Processing starts with a first server receiving the http request from the terminal (9010), where it is assumed that this request comprises the relevant AID (RID and PIX portions). This first server extracts the RID portion 501 from the received AID (9020), and uses the RID to determine the URL of a second server (9030), generally by means of a database or lookup table available to the first server (either locally or over a network). The first server therefore can be considered as representing a form of generic gateway or portal, and the RID as a form of search term submitted to the portal.

Once the first server has determined the identity of the second server, the first server now in effect forwards the incoming request to the second server (9040). It is assumed that the second server is associated with the particular organization corresponding to the relevant RID. In other words, an organization having the RID in question maintains a web site on the second server. This web site is responsible for receiving and processing AID strings belonging to that organization (i.e. having an RID portion corresponding to that organization).

The AID string from the terminal is therefore received at the second server from the first server (9045), and decoded using an appropriate AID interpreter or other mechanism. (It is assumed that the organization knows how to decode its own AID strings). Using the information obtained from the decoded AID, the second server now identifies a Java Application Descriptor (JAD) file (9050) to be used by the terminal in processing the smart card. The JAD file is generally retrieved from a stored set of such files, but might also be built dynamically in response to the terminal request.

According to one embodiment, the identified JAD file comprises a URL or other reference indicating the location of an AID interpreter. The terminal can then use this reference to download code for decoding and processing the AID itself. The JAD file can also contain any other appropriate information, code references, descriptors, etc that may be required or useful for the session.

The second server now places the JAD file at a network-accessible location, and returns a URL for this location to the first server (9060). The first server duly receives the URL (9065), and in turn forwards the URL back to the terminal (9070). This URL therefore allows the terminal to retrieve the JAD file constructed by the second server, and then to download any code that it references.

Note that there are several possible variations on the processing of FIG. 9. For example, instead of initially returning a URL for the JAD file from the second server to the terminal (via the first terminal), in other embodiments the JAD file itself can be transmitted along this route. A further potential variation is that at 9040 the first server returns to the terminal the URL of the second server. In this approach, the terminal itself is then responsible for communicating directly with the second server, rather than using the first terminal as an intermediary. If so desired, this can be implemented in a straightforward manner by using the http re-direct mechanism.

FIG. 10 depicts an environment in which the procedures of FIGS. 8 and 9 can be implemented in accordance with one embodiment of the invention. Thus applet 351 is installed on card 102, and incorporates AID 401 and card AID interpreter 411. When the card is engaged with terminal 110, the AID 401 for the desired application is extracted from applet 351 and passed to terminal 110 (such as previously described in relation to FIG. 6, for example).

Within terminal 110, the AID 401 is split into its two main constituents, namely RID 501 and PIX 502. The former portion (i.e. RID 501) is used to key into a lookup table 810, which contains a mapping of RID to URL. Based on the RID extracted from AID 401, a corresponding URL 805 can then be determined from the lookup table 810. This URL corresponds (in this particular situation) to a download site 860 for code to be used in processing the session involving card 102. A request 805 for such code is therefore sent to the download site 860. Note that this request may incorporate the full AID string received from the card. This AID string (or portions of it) can then be used by the download site to identify particular code of relevance for this session.

In response to the code request 805, a code package 806 for interpreting the AID 401 is returned over network 850 to terminal 110. This code package is then installed into terminal 110 to form a proxy AID interpreter 811. The newly installed code allows the proxy AID interpreter 811 to retrieve and interpret the data encoded in PIX 502 portion of AID 402, thereby permitting the terminal to continue processing the session with the card 102.

Proxy AID interpreter 811 on the terminal 110 comprises code that is analogous to or shared with AID interpreter 411 on the card, and may potentially be a superset (subclass) of the card AID interpreter 411. Note that proxy AID interpreter 811 is generally not only able to extract a firewall and applet identifier from PIX 502, but it is also able to access any other pertinent information that may be encoded into the PIX 502. (This additional information might relate to the state of the application on the card, such as described above in relation to FIG. 5).

FIG. 11 illustrates another embodiment, which is similar to that of FIG. 10, but this time a slightly more complex chain of operations is involved for the terminal 110 to obtain the code for processing a session. Thus in this embodiment, there is a mapping process 810A that converts the RID received from terminal 110 into a first URL, this time corresponding to portal site 862. The terminal directs a query 805 to this portal site. According to one embodiment, the query comprises the AID of applet 351. In other words, the AID is incorporated into the URL associated with the request to portal site 862 (generally in an analogous manner to the way that a search string is supplied to a web search engine).

The portal site 862 responds to the incoming query 805 by providing in return the URL 805A of the code download site 860. In the particular embodiment of FIG. 11, portal site obtains this URL from database 865 using the received AID or at least a portion of it, such as the RID, as an index into the database 865. The code download URL 805A is therefore received back at terminal 110 from portal site 862.

The terminal now generates a code download request 808 directed to the received code download URL. Note that the terminal 110 may potentially comprise the AID in this code download request 808. The code download request 808 is received at code download site 860, which returns code 806 corresponding to the particular URL of the request. One use of this code download mechanism is to allow the terminal 110 to install its own proxy AID interpreter 811, for use during the session with applet 351, as described above in relation to FIG. 10.

Note that the code downloaded from site 860 to terminal 110 may be dependent upon the AID (if any) included in code download request 808. For example, the AID might contain membership details for the cardholder. The code 806 for download can then be selected so as to only offer services appropriate to the particular class of membership of the cardholder (as determined from the AID).

It will be appreciated that it is generally easier to maintain a single network-accessible database 865 of RID to URL mappings, such as depicted in FIG. 11, than to have separate mappings 810 stored in each terminal, such as depicted in FIG. 10. On the other hand, the approach of FIG. 10 is generally faster than that of FIG. 11, given the reduced number of network requests involved. One compromise therefore is to adopt a hybrid approach, in which lookup table 810 represents in effect a local cache of data from code URL database 865. In such an embodiment, terminal 110 first attempts to find the location of code download site 860 using lookup table 810. According to one embodiment, this table stores the mappings for recently processed RIDs. However, if no entry for the RID in question is found in the lookup table, the terminal then contacts portal site 862 to derive the location of code download site 860 from database 865 (which is assumed to be much larger and more complete than lookup table 810). Any mapping information obtained in this manner from the code URL database 865 may be added into the lookup table 810 for future use (depending on the particular cache occupancy strategy deployed).

It will be appreciated that the ability to download onto a terminal 110 a proxy AID interpreter 811 that is specific to the particular AID of the inserted card 102 complements the initial AID matching procedure described above (see e.g. FIGS. 6 through 6F). Thus the provision of card AID interpreter 411 on the card 102, and the use of Applet ID and Firewall ID (rather than the AID byte string itself) to specify a desired applet 351, allows a terminal to obtain the AID of the desired applet without needing to know (initially) the specifics of the AID itself.

Similarly, rather than having to preinstall appropriate AID processing software on all terminals, the AID obtained from the card can then be used by the terminal to identify and acquire a proxy AID interpreter 811 that is able to parse and manipulate the AID in question. According to one embodiment, the appropriate proxy AID interpreter 811 is downloaded over a network onto the terminal in order to complete the relevant session with the card 102. Accordingly, the dynamic provision of a proxy AID interpreter to a terminal helps to allow the PIX portion 502 of an AID to be used for more complex and varied tasks, which may perhaps be modified over time, without compromising compatibility at the set of terminals already present in the field.

Note that there are many potential variations on the embodiments of FIGS. 10 and 11. For example, a default structure may be defined for AID 401. Terminal 110 then has preinstalled a proxy AID interpreter 811 that is able to parse and extract information from an AID conforming to this default structure. In this case, there may be no need to derive a network resource identifier from an RID in this AID. For example, in the embodiment of FIG. 10, lookup table 810 may instead indicate that the default proxy AID interpreter is to be used (perhaps by simply having a null entry for that RID). This can be regarded as analogous to the processing of FIG. 8E.

On the other hand, in the embodiment of FIG. 11, the RID to URL mapping (box 810A) may still be performed, but the response from the portal site 862 then indicates that the default proxy AID interpreter is to be used. In this case there is no need for the terminal to send a subsequent code download request 808, assuming that the default proxy AID interpreter is already installed on the terminal.

A further possibility is that the terminal attempts to use the default AID interpreter 811 if it is unable to find any other suitable code for this session, for example because there is no entry for the RID in the lookup table 810 or the portal site 862 (depending on the particular embodiment) or because a network connection is currently unavailable. Alternatively, the lack of a positive indication of which proxy AID interpreter for the terminal to use for a given AID (default or otherwise) might be taken as an error, possibly causing the terminal to abort the session.

FIG. 11A is a flowchart illustrating the operation of one embodiment of the invention in which the terminal may utilize a default proxy AID interpreter. The method starts with the terminal obtaining the AID from the card (reference numeral 1110, corresponding generally to reference numeral 8020 in FIG. 8). The terminal now determines whether the RID corresponds to the default interpreter (1120). If not, then the terminal attempts to download the AID interpreter corresponding to the RID, as previously described in relation to FIGS. 8 and 11 (1130). A test is now performed to see if this download has been successful (1140). If so, then the downloaded AID interpreter can be used for the session (1150). Alternatively, the default AID interpreter is used (1155) if this is the one indicated by the RID received from the card at 1120, or if the download was unsuccessful at 1140. The terminal now continues to process the session with the card (1160). Note that there may be certain restrictions on the functionality available during such processing if the default AID interpreter is being used because the specified AID interpreter is unavailable (i.e. the test of reference numeral 1140 was negative).

It will be appreciated that even for those cases where there is a specific proxy AID interpreter to use for a particular AID string, this will frequently be formed as a modification of the default proxy AID interpreter. For example, code obtained from a location such as code download site 860 can comprise a plug-in for the default proxy AID interpreter, or may be utilized via any other suitable mechanism. Alternatively, the downloaded code may subclass portions of the default proxy AID interpreter in order to provide more specific functionality in certain areas.

One implication of the ability to acquire a proxy AID interpreter 811 within the terminal 110 itself is that this now offers the possibility of performing the initial AID matching in the terminal 110 (in contrast to the AID matching performed on the smart card 102, such as illustrated above in FIG. 6). One embodiment of the invention which supports such processing is illustrated in the flowchart of FIG. 12, which commences in the same general manner as the flowchart of FIG. 1. In other words, the terminal detects insertion of the card (162), and consequently activates the card (reference numerals 164, 172).

At this point however, rather than specifying a desired application in terms of RID, Firewall ID, and Applet ID (corresponding to reference numeral 8005 of FIG. 8), instead the terminal requests the applet selector 412 to provide it with the full set of AIDs for the card—i.e. the AID for each available applet 351 on the card (1245). The applet selector receives this request (1254), and according to one embodiment, uses a get_AID( ) method call on the card AID interpreter 411 of each application installed on the card in order to retrieve the AID for that application (1256). The precise manner in which the get_AID( ) call is implemented will depend upon the internal details of the card AID interpreter 411 in question (as discussed above in relation to FIGS. 5A, 5B, 5C, and 5D). Note that prior to making the get_AID( ) call for an application, the applet selector may first have to call the applet itself in order to locate the card AID interpreter 411 for that particular applet (analogous to reference numeral 681 of FIG. 6). Note also that the AIDs for different applications may be collected in parallel, or one after another, or via any other suitable strategy.

The AIDs for the card applications are now returned from the card 102 to the terminal 110 (reference numerals 1258, 1246), where the RID is extracted from each AID (1247). This RID then allows the terminal to identify and to acquire (if necessary) a proxy AID interpreter 811 to be used in processing the corresponding AID (1248). Note that the same procedure can be used here to obtain the appropriate proxy AID interpreter 811 as described above in relation to FIGS. 8 and 9. (It will be appreciated that there may be a different proxy AID interpreter 811 to download for each application 351 on card 102).

Once the terminal has the appropriate proxy AID interpreter for an AID, it can now decode that AID to determine the Firewall ID and Applet ID encoded into the AID. This then allows the terminal to perform the matching of RID, Firewall ID and Applet ID in order to identify a desired application for use in this particular session (1249). The proxy AID interpreter 811 can adopt the same procedure to identify a matching application as described above in relation to card AID interpreter 411 on the card itself (see FIG. 6). After this matching has been completed, the terminal notifies the card (reference numeral 182, see also FIG. 1C) of the applet that matches the above parameters (RID, Firewall ID and Applet ID). According to one embodiment, this is achieved by returning the (complete) AID of the desired matching application from the terminal 110 to the smart card 102. This then allows the card to launch the specified matching applet (reference numeral 190, see also FIG. 1C again).

One advantage of performing parameter matching on the terminal instead of on the card is that resources (memory, processing power, etc) are much more readily available on the terminal than on the card. On the other hand, there is the potential as mentioned above of having to download multiple AID proxy interpreters onto the terminal, one for each applet on the card, which may be relatively time-consuming. In practice however, the number of proxy AID interpreters to download can be significantly reduced by looking at the RID 501 obtained by the terminal at 1247. If this RID matches the RID of the application desired by the terminal, then the terminal proceeds to obtain a proxy AID interpreter 811 for the associated AID. However, if the extracted RID does not match the RID of the application desired by the terminal, then there is no need to download the corresponding proxy AID interpreter 811, since this application cannot represent the desired application. Consequently, reference numeral 1248 need only be performed with respect to those AIDs that contain a matching RID, thereby greatly reducing the number of proxy AID interpreters to be downloaded to the terminal.

This situation is depicted in FIG. 12A, which illustrates in more detail some of the processing of FIG. 12. (The dotted box in FIG. 12A corresponds to the box of the same number in FIG. 12). According to one embodiment, the procedure of FIG. 12A is performed in respect of each AID byte string received by the terminal 110 from the card 102.

The procedure of FIG. 12A commences with the extraction of the RID from the AID (1247), as previously discussed in relation to FIG. 12. A test is now performed to see if the RID for this received AID matches the RID of the desired application (1212). If not, then it is known that it is not desired to activate the applet on the card from which this AID has been received, and so the AID can be discarded, or other appropriate action taken (1230).

Assuming however that there is an RID match, the terminal now has to determine which proxy AID interpreter to use for the AID (1214), whereupon the relevant proxy AID interpreter is identified and installed onto the terminal (1216) (if it is not already present). Note that the identification and installation of the desired proxy AID interpreter is generally driven off the RID, as described above in relation to FIGS. 8 and 9. The proxy AID interpreter 811 is now initialized with the corresponding AID string from the smart card 102 (1218), which then allows it to proceed with the parameter matching of reference numeral 1249.

FIG. 13 depicts a variation on the embodiments of FIG. 6 and FIG. 12. The embodiment of FIG. 13 commences as these other two embodiments, with the terminal detecting insertion of the card (162), and then activating the card in response to such detection (reference numerals 164 and 172). Next, the terminal requests not only the set of AIDs from the card, but also the three application identifying parameters for each application—i.e. the RID 501, the Firewall ID 502A, and the Applet ID 502B (1345). The applet selector on the card receives this request (1354), and responds by calling the get_AID( ), get_RID( ), get_FirewallID( ) and get_AppletID( ) methods for each applet (1356). Again, this may involve an initial call to the applet in question, in order to locate the card AID interpreter 411 for that applet (as shown in FIG. 6).

(Note that for clarity the AID and the RID are treated separately here, with two distinct calls being made to obtain them. However, it will be appreciated that since the RID is encoded in a fixed position within the AID, these two can be handled by a single operation. In other words, there is no particular need to make a get_RID( ) call, but rather the RID can be obtained as and when required from the first five bytes of the retrieved AID).

The applet selector now returns the set of parameters for each applet back to the terminal (reference numerals 1358 and 1346). The terminal matches the parameters received from the card against the parameters for the desired application (1347). Note that because this matching is being performed using parameters supplied from the card, rather than the terminal itself having to derive the parameters from the AID string (as in the procedure of FIG. 12), there is no need at this stage for the terminal to have the relevant proxy AID interpreter(s) 811 installed or downloaded.

In one embodiment, the terminal 110 has just a single application to match. Once this (single) application has been identified at 1347, processing can now proceed to 182, where the terminal instructs the card to launch this applet (for example by providing its full AID), with the card then responding accordingly (179).

The proxy AID interpreter 811 corresponding to the selected applet may be pre-installed on the terminal. This is particularly likely if the terminal 110 only supports a single application, since in this case only one proxy AID interpreter 811 will generally be needed, but may also apply if the terminal supports multiple applications. In alternative embodiments, the terminal downloads the proxy AID interpreter 811 for the matching application either before, during, or after reference numeral 182. (The download of the AID interpreter is not shown in FIG. 13, but can be as illustrated with respect to FIG. 8 or 9, and the subsequent installation and initialization of FIG. 12A).

It will be appreciated that the precise timing of any such download of a proxy AID interpreter 811 to terminal 110 is based at least in part on the particular selected application. For example, the AID string may contain some data value that affects the start-up or operation of the applet on the card at 660. In these circumstances therefore, the proxy AID interpreter 811 should be available on terminal 110 to decode this data value before the terminal can send the appropriate applet launch command to the card at 182.

In the embodiment shown in FIG. 13, multiple applications may be matched at 1347. For example, in one embodiment the terminal tries to identify all those applications that are present on the card that the terminal could potentially interact with (i.e. conduct a commercial transaction with). Accordingly, if there is a first set of applications installed on the card, and a second set of applications supported by the terminal, then at 1347 the terminal identifies the intersection of these two sets (such as by looking for matching parameters, namely RID, Firewall ID, and applet ID).

The terminal now presents a choice or listing of these matching applications to a user, for example as a menu on a touch screen (1348). This enables the holder of a multi-function card 102 who is acting with a multi-function terminal to select the particular application to be used for this session (1349), again perhaps by using a touch-sensitive screen at a kiosk terminal. (More generally, the user would select the desired type of service or operation, and the terminal would then invoke the application corresponding to this form of service). The terminal now informs the card of the application that has been selected by the user (182), allowing the card to launch this application accordingly, as previously described (190).

It is also possible for the procedure of FIG. 12 to be modified in order to provide an opportunity for a user to select a desired application. In this case reference numeral 1249 could represent a determination of those applications mutually supported by both the terminal and the card, with the user then selecting one of these applications. The terminal then informs the card of which application to launch, as described above in relation to FIG. 13 (reference numerals 182 and 190).

However, such a procedure would generally involve the terminal downloading multiple proxy AID interpreters 811 in order to allow parameters (Firewall ID, etc) to be extracted from the various AIDs received from the applications on card 102 (as per reference numeral 1248 of FIG. 12). In contrast, download of the proxy AID interpreters 811 to the terminal 110 can be deferred in the procedure of FIG. 13 until after the user has selected a desired application (1349). At this stage, there is only a single proxy AID interpreter 811 to download. (This download is not shown in FIG. 13, but may occur before, during or after the launch of the selected applet).

In some circumstances, it may be that the presentation of options to a user (1348) is dependent on information encoded into the AID (other than the RID, Firewall ID and Applet ID components received from the smart card itself). For example, an AID may incorporate an expiry date encoded into Other portion 502C, after which the associated application is no longer available to the user. For this type of situation, one possibility is to download the proxy AID interpreter 811 for the application (such as by using the method of FIG. 8) prior to presenting the user with the set of available options (i.e. before reference numeral 1348). This then allows data from the various AIDs to be decoded by the respective proxy AID interpreters, and used to tailor suitably the options presented to the user at 1348. For example, if an application expiry date has passed, the corresponding application can then be omitted from the list of applications presented to the user.

It will be noted that such an approach again requires potentially multiple AID interpreters to be downloaded to terminal 110. This can be avoided by having the additional information (such as an expiry date) accessed and decoded by the card AID interpreter 411. As previously described, the card AID interpreter 411 generally knows how to unpack such additional components of the AID, even if it does not know what the additional components represent or how to process them.

For example, at 1356, the card AID interpreter 411 may obtain not only the RID, Firewall ID and Applet ID, but also an expiry date encoded into the AID. (From the perspective of the card AID interpreter 411, the expiry date is generally simply an additional piece of abstract data encoded into the Other portion 502C of the AID 401). This expiry date can then be supplied by the card to the terminal at 1358, along with the RID, Firewall ID and Applet ID. The terminal can then use this additional parameter as appropriate in further processing (for example, in making a decision as to whether or not the corresponding application is available for the cardholder to use). Note that such processing does not necessarily compromise the generality of the terminal, since the terminal does not need to know how the additional information (e.g. the expiry date) is encoded into the AID itself. (The terminal may already know that the parameter exists, and how to interpret the parameter, in order to be able to interact properly with the application).

Another implication of the provision of multi-function terminals, i.e. terminals supporting a number of applications, is that each application has its own associated proxy 410 and associated back office program 130 (see FIG. 4). Thus if a terminal supports only a single type of card application, then the proxy for this application can automatically be invoked on terminal 110 in response to the insertion or activation of card 102. Indeed, the proxy may only be sleeping or suspended between sessions with different cards.

On the other hand, if the terminal supports multiple applications, there may be a different proxy for each application. In this case, where the cardholder is able user to select the particular application to be used with the inserted card (such as discussed above in relation to FIG. 13), then the terminal needs to ensure that the correct proxy is invoked to handle the user selected application.

In these circumstances, the terminal can be provided with a program (not shown in FIG. 4) analogous to the applet selector program, which is used to determine the appropriate proxy to handle any given card session. In the embodiment of FIG. 13, this selector program is responsible for the interaction with the card through to receipt of the user selection of the desired application (1349). At this point, the selector program can then launch the proxy corresponding to the user selection. The proxy 410 can then download the corresponding proxy AID interpreter (if not already present), as well as launching the selected application on the card (reference numerals 182 and 190).

FIG. 13A presents a flowchart depicting the selection and activation of a proxy program on terminal 110 in accordance with one embodiment of the invention. Note that this procedure can be regarded as following on from the flowchart of FIG. 12, whereby it is assumed that the proxy AID interpreter 811 corresponding to a particular AID (and corresponding applet) on the smart card 102 has already been installed and initialized on the terminal 110. In this case, the procedure of FIG. 13A commences with a determination of the proxy to be used with this application (1330). Such a determination can be made based on material retrieved over the network (see FIGS. 8 and 9 above and associated discussion), or alternatively the terminal may have local knowledge of the proxy to use with this particular application. Another possibility is that a proxy itself contains information (such as the RID, and perhaps other parameters as well) that allow the proxy to be matched to a corresponding card application

Once the terminal has identified the correct proxy 410 for use with the relevant application, this proxy is installed into the terminal (1332), unless it is already present. Thus the proxy code can be obtained over a network, in the same manner as the proxy AID interpreter code 811 (see FIGS. 10 and 11). The proxy code can now be initialized with the proxy AID interpreter code that has already been downloaded (1334), which in turn can be initialized with the AID received from the application (such as at reference numerals 1246 or 1346). This leads to the general configuration of FIG. 4, whereby substantive processing of the user session can commence.

As already discussed, the approach described herein permits a more flexible and powerful use of an AID 401 on a smart card 102. One further mechanism for exploiting this increased flexibility is to use the AID to store information concerning the initial configuration of an application at load time.

FIG. 14 is a flowchart that depicts such a process in accordance with one embodiment of the invention. The process of FIG. 14 begins with loading the Java classes for an applet 351 onto the smart card 102 (1010). According to one embodiment, these classes are assembled into a package (referred to as a CAP file). Once the classes are present in memory on the smart card 102, then instantiation commences (1020). In other words, objects are created based on the class files. Note that in a smart card environment, this instantiation is a one-off procedure at load time, rather than being performed each time the applet is executed, as in a normal desktop environment. Object instantiation is followed by initialization of variables (1030), and then configuration of the applet occurs (1040). Finally, any other necessary initialization and personalization completes (1050), whereby the card is now ready for use.

FIG. 15 illustrates certain aspects of the procedure of FIG. 14 in more detail, in particular the role of the AID in the card configuration process, in accordance with one embodiment of the invention. Note that the dotted outline boxes in FIG. 15 correspond to reference numerals from FIG. 14.

Thus as part of the instantiation process of reference numeral 1020, the card AID interpreter 411 is created (including the AID object hierarchy such as shown in FIGS. 5A, 5B, 5C or 5D). According to one embodiment, this is achieved by calling appropriate methods (such as a factory method) on the applet being installed in order to instantiate the card AID interpreter 411 (1510).

The configuration program now generates the actual AID value to be stored into the card as part of the initialization (reference numeral 1520 in FIG. 15). (There is some flexibility in the timing of reference numeral 1520, for example, in some embodiments the creation of the AID may precede the creation of the card AID interpreter at 1510). The newly created AID value can be used to encode various configuration data relating to the application that is being installed. Examples of configuration data that may be stored in the AID in this manner include: an indication of the physical and/or software capabilities of the card (e.g. memory capacity, and whether a certain format of digital signatures is supported, the version number of an installed application, etc); general parameters governing card behavior, such as passwords and key lengths; and parameters relating to more application-specific properties, such as the maximum amount of money that may be stored in a purse object, or the maximum payment amount that may be made using the card without requiring a Personal Identification Number (PIN). It will be appreciated that multiple items of various configuration data can be incorporated into a single AID, subject to the available space limitations (in particular the 11 byte limit on the PIX portion of the AID).

Once the AID for the card and the program being installed has been generated by the configuration program, this is now passed to the card AID interpreter 411 (1530). In particular, a store_AID( ) method (or similar) is called on the card AID interpreter, and this is passed the AID string that was generated at 1520. The card AID interpreter then acts to save the newly received AID string onto the card. The manner in which this is accomplished will depend upon the internal implementation of the card AID interpreter and how the AID is to be stored (such as depicted in FIGS. 5A, 5B, 5C and 5D). For example, in one embodiment the AID string is ultimately saved as a single byte array (as in FIG. 5A), or may be distributed into multiple components, each associated with a different AID subobject (as in FIG. 5B).

According to one embodiment, a security procedure associated with storing the AID, to ensure that a duly saved AID is not subsequently corrupted (either deliberately or accidentally) by an inappropriate repeat call of this facility. For example, some form of password can be required to use the store_AID( ) command, or alternatively the store_AID( ) command is perhaps only enabled at applet installation time.

Once the AD has been stored onto the card 102, the AID can then be accessed during subsequent configuration of the applet in order to derive the configuration information encoded into the AID (1550). According to one embodiment, the AID is accessed by making an appropriate call on the card AID interpreter 411. In one embodiment, this involves making a get_ABD( ) method call on the AID interpreter, such as previously described, and then extracting the desired configuration information from the AID string. However, this generally requires the applet itself (or other configuration facility) to be able to decode the configuration information encoded into the AID. Thus in another embodiment, the card AID interpreter 411 itself decodes the configuration information stored in the AID string. Accordingly, in this embodiment the card AID interpreter 411 supports one or more method calls that provide specific access to configuration information from the AID string.

For example, the card AID interpreter 411 can support a get_AIDConfiguration( ) method call, which returns the full set of configuration data from the AID string, appropriately organized into a data structure or such-like. Alternatively, the card AID interpreter 411 can include a subobject which provides access to such data. It is also possible that the card AID interpreter 411 supports calls to access individual components of configuration data stored in the AID, e.g. a get_CardMemoryo to retrieve the memory capacity on the card, although this tends to lead to a rather more complicated method signature for the card AID interpreter.

Once configuration data has been retrieved from the AID in this manner, this configuration data can then be used to control the particular software and data configuration adopted for the applet (1560). Examples of configuration data that can be stored into the AD include parameters that determine the characteristics of cryptographic algorithms used on the card (e.g. number of bits); memory usage (e.g. the number of bytes of card memory allocated to the application); the version number of various software support modules on the card; and so on. Making this information available to an applet via its AID helps to ensure that the installed applet conforms to properties of the smart card in question concerned (for example, the applet does not try to use more memory than is allocated to it on the card).

The above procedure therefore allows information about the card and the applet instance in the card environment to be encoded into the AID. This information can then be used to control the particular configuration of the applet as it is being installed. It will be appreciated that this provides a convenient software mechanism for optimizing the application configuration for the relevant environment, without having to depart from a relatively conventional or standardized loading procedure. In other words, rather than having to customize the installation process itself, any special configuration details can be encoded into the AID. The AID information can be used to control the precise configuration adopted without further external intervention, so that the applet instance is matched to the particular card on which the applet is installed, with different applet code or configurations being installed on different cards.

Attached to the present description is a set of Appendices. These provide documentation relating to one implementation of certain components described herein. Various features are detailed that are not necessarily relevant to the invention itself (although they are typical of a complete implementation). Nevertheless, the Appendices provide the skilled person with a general indication at the code level as to how an implementation may be developed.

Appendix A describes a card AID interpreter (corresponding for example to card AID interpreter 411 in FIG. 4). Note that in this implementation, the Firewall ID 502A (see FIG. 5) is stored in byte 6 of the AID, and the Applet ID 502B is stored in byte 7 of the AID. An Owner ID is then formed as the composite of the RID 501 and the Firewall ID 502A, while the Applet ID is (re)defined as the composite of the Owner ID and the Applet ID 502B. Applet selection can then be performed using the Applet ID (only), since this incorporates the RID 501, the Firewall ID 502A and the Applet ID 502B of FIG. 5. Note that from a logical perspective however, the selection is still utilizing these three parameters, which can be regarded as encoded into the (redefined) Applet ID.

With the particular byte allocations described in Appendix A, the RID, Owner ID and the Applet ID correspond to the first five, six and seven bytes respectively of the AID. However, in other implementations they may be encoded differently into the AID (except of course for the RID, whose location is governed by the ISO standard).

Appendices B, C, D and E describe four classes nested within the AID interpreter that respectively manage the various components of the AID, such as the RID portion, the Owner portion, and so on. This is somewhat analogous to the embodiment illustrated in FIG. 5C.

Appendix F describes a proxy AID interpreter (corresponding for example to proxy AID interpreter 811 in FIG. 4). Note that there is a predefined list of attributes that might potentially be encoded into an AID (and hence need interpreting). Attributes that are not supported by a particular card are set to null. Additional attributes may be supported by suitably extending the class of Appendix F.

Provided below is a summary of selected embodiments of the present invention.

According to one embodiment of the present invention, a method for installing an application onto a smart card is provided. The method includes providing an application identifier (AID) for the application. The AID includes at least one customization parameter for the application to be installed. The method further includes instantiating the application onto the smart card and storing the AID for the application onto the card. The application is now configured in accordance with the stored AID, and more particularly, in accordance with said at least one customization parameter.

The AID can therefore be used to supply configuration information to control the installation of the application onto a smart card. One advantage of this approach is that it helps to provide a consistent and self-defining installation process that is not reliant upon external parameters or settings (other than as recorded in the AID itself).

A wide variety of customization parameters can be handled in this manner. For example, the parameters may relate to one or more resources available to the application on the card, such as allocated memory or cryptographic facilities. Another possibility is that a customization parameter is indicative of a level of service to be made available to a cardholder in transactions involving the application. The application is then configured to allow for the settings or values of such configuration parameters.

According to one embodiment, the application includes an AID interpreter. As part of the installation process, the AID is passed to the AID interpreter, which then stores the AID for the application onto the card. Subsequently, when configuring the application, the stored AID can be accessed with the AID interpreter, which extracts the customization parameter(s) from the stored AID. In one embodiment this involves instantiating the AID interpreter by calling a method on the application during instantiation of the application itself. This then allows the AID for the application to be stored onto the card as part of initialization of the application.

Another embodiment of the invention provides apparatus for installing an application onto a smart card. The apparatus includes an application identifier (AID) for the application. The AID includes at least one customization parameter for the application to be installed. The apparatus further includes an install facility operable to instantiate the application onto the smart card and to store the AID for the application onto the card. The application is configured in accordance with the at least one customization parameter from the stored AID.

Another embodiment of the invention provides a computer program product comprising instructions on a medium. When loaded into a machine, the instructions cause the machine to install an application onto a smart card. This involves providing an application identifier (AID) for the application. The AID includes at least one customization parameter for the application to be installed. The application is then instantiated onto the smart card, and the AID for the application is stored onto the card. The application is now configured in accordance with the stored AID, and more particularly in accordance with the customization parameter.

Note that a computer program product may comprise program instructions stored on a removable storage medium, for example an optical (CD ROM, DVD, etc) or magnetic (floppy disk, tape, etc) device. Such a medium can then be introduced into a computer system in order to transfer the program instructions to the system. Alternatively, the program instructions may be transferred to the computer system by download via a transmission signal medium over a network, for example, a local area network (LAN), the Internet, and so on. According to one embodiment, the transferred program instructions are stored on a hard disk of a computer system, and loaded for use into random access memory (RAM) for execution by a system processor.

It will be appreciated that the apparatus and computer program product embodiments of the invention will generally benefit from the same particular features described above as the method embodiments of the invention.

While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.

Appendix A

Class AID

All Implemented Interfaces:

Readable, java.io.Serializable

Direct Known Subclasses:

SunAIDEncoding

public class AID

extends javacard.framework.AID

implements Readable, java.io.Serializable

A representation of the Application Identifier with support for a Java Card standardized encoding of additional data in the PIX field. This class and the complementary AID interpreter class provide a key functionality for generic support of card application management and application interoperability in the Java Card application framework. This class explicitly provides enhanced support for the selection of Java Card Applets by the terminal using a partial AID.

In particular this class provides support for the following distinct data elements associated with the Applet which are encoded in the ISO standardized AID byte[ ] representation (see below for the default encoding scheme):

-   -   1. It specifies the application provider as a legal entity (via         the RID), as defined by ISO/IEC 7816-5. By convention, in the         Java Card implementations only nationally or internationally         registered RIDs are formally supported.     -   2. It specifies the in-card instance of the Java Card “firewall”         that contains the Applet and all the objects the Applet uses to         store its data. Or, in more appropriate terminology, it         specifies the “owner” of the Applet and Applet data objects         instances in the card. The owner of an applet is commonly         referred to as the Application Provider. To complicate matters,         in principle, the legal entity identified by the RID in an AID         may be present in the card as multiple different owners.

For example the RID may identify an organization that is both the card issuer and provider of an application. In this example the card management operations performed by the card issuer applet should be separated by a firewall from the application operations implemented by the application Applet. The Ownership information is encoded in the PIX field as an extension of the RID.

-   -   3. It specifies a unique applet within a firewall,         distinguishing it from any other applets that may be         instantiated in the card with the same owner. This information         is used for selection of applets. This information is encoded in         the PIX field as an extension of the owner.     -   4. It specifies specific functions for applets of the same         owner. For instance with distinct functions possibly indicated         for a pre-paid (purse), debit (ATM) card or credit card applet.         Similar function indications have been adopted by ISO 14443 for         contact less cards as Application Function Identifiers (AFI).         The interpretation of this code can be standardized by industry         segment bodies.

This information is contained in the PIX field.

-   -   5. It may specify additional information on the applet code,         like code version numbers, for instance to complement the         specified function. This information is optional. This optional         information will be encoded in the PIX field.     -   6. It may specify additional information on the applet data         instantiated in the card like key (batch) identifiers, or         configuration data like the number and kind of supported data         sets. This AID data element refers to Applet instance data that         may vary per applet instance, but that does not, or rarely         change over the life time of that instance. This data may be         used by the applet at installation time to configure it self.         When retrieving an AID from the card part of the code space for         this data may be used to encode applet state data (see next         item) This optional information will be encoded in the PIX         field.

7. It may specify additional information on the applet instance state data like the currency and value of the balance in a purse, or a currently assigned “service level” as may be found in a loyalty scheme. This AID data element refers to Applet instance data that is different in each applet instance and that may vary in each selection of the applet. This optional information will be encoded in the PIX field. The encoding space for this data in the PIX may be the same (as a part of) the configuration data (see previous item).

In this design each applet provides its own derived class with appropriate implementations of the abstract methods. The OwnerID is different from the RID as according to ISO rules an organization can only obtain a single RID. But, the card issuer may also be the provider of an applet on the card but may want to specify different owners for the loading Applet (function) and the other applet. And also, the issuer may want to distinguish ownership of library packages from both the loading applet and the other applet. Similarly, the AppletID is different from the OwnerID, as the same owner may have more than one collaborating applet, where each applet is specified by the owner as selectable separately.

Encoding and Interpretation

The encoding and interpretation of the data elements actually contained in an AID may in general be specific to the application provider (registered entity). However, this AID class provides a default encoding for the first, non optional, data elements contained in the PIX as described below. The encoding of optional data elements in the PIX field is not defined, and must be specified in a sub class of this class when such optional data is required. This class provides the framework for such optional data to be used. The in-card interpretation of the optional instance data, and possible use of this data for install-time configuration is not specified here. However, an abstract class is provided as a basis for the representation in the card of such configuration information.

Interpreting the AID information in a terminal may be accomplished by using the AID interpreter instance. Typically, a sub class of the AIDInterpreter class will be used to represent any of the optional data elements. The AID interpreter may be provided to the terminal via a provisioning mechanism that uses the unique value of the RID in any given AID. Interpreting the data encoded in the AID by that class might involve retrieving data from the world wide web.

Applet Selection, Firewall and Ownership

The AID class provides explicit support for selection of applets by partial AID with the implementation of the methods #matchId( ), #matchOwner( ) and #matchRID( ). The mechanism provided by these methods addresses the issue of partial matching which has been left underspecified in version 2.1 of the Java Card technology specifications.

An implementation of the Select Applet command may use these methods by examining all Applets in a card in a sequence of increasingly less specific matches. First the applets are tested for a matching applet identifier, using the matchId( ). If no Applet has been identified the applets are tested for a match on the owner ID using matchOwner( ). And finally, if that does not identify a single Applet, all Applets are tested for a match on the RID using matchRID( ). This three stage matching algorithm provides full functional backward compatibility with Applets that are implemented with the javacard.framework.AID class (version 2.1).

Encoding

The AID class provides a default encoding of the AID in a sequence of maximally 16 bytes. The encoding follows the following rules (see the diagram):

-   -   1. The RID is encoded as defined by the international standard         ISO/IEC 7816-5 over the first five bytes of the AID encoding.         The AID implementation fully conforms to this international         standard.     -   2. The OwnerID is encoded as the first six bytes of the AID         encoding, thus including the RID. The value encoded in the         additional byte is not specified here and will be allocated by         the entity identified by the RID. The purpose of this value is         to distinguish between the different commercial and/or         functional roles the registered entity may have in the card that         require separation by a firewall.     -   3. The ApplicationID is encoded as the first 7 bytes of the AID         encoding, thus including the OwnerID. The value encoded in the         additional byte is not specified here and will be allocated by         the entity identified by the RID. The purpose of this value is         to distinguish between specific applets on the card that share         the same owner and firewall, such as a Debit Card applet and a         Credit Card applet provided by the same financial institution.     -   4. The Application Function ID is encoded on the 8th byte in the         AID encoding. The value of this byte is encoded according to         international standard ISO/IEC 14443 (contact-less cards).     -   5. The optional applet version, configuration and applet state         data are encoded over the remaining 8 bytes of the AID. The         applet AID matching algorithm that may be used in applet         selection excludes these data elements. There is no default         encoding for these optional data elements.         -   An encoding for the configuration data is specified by the             implementation of a sub class of the inner class AID.             ConfigurationData The concrete configuration data class in             the Applet may be used at applet-install time only or, in             the implementation of a possible APDU handler to decode             configuration data during the operational phase.         -   Using Applet state data in an AID retrieved from the card is             supported with a method call. This method has a default             empty implementation. The method is intended to append a             byte[ ] representation of the selected Applet state data to             the AID encoding when it is being read by a terminal.             In order to use either version data, configuration data or             applet state data a sub class of this class must be defined             that overrides the relevant methods, getVersion( ),             getConfiguration( ) and readStateBytes( ), respectively.

The default encoding of the data elements defined by the AID java class is summarized in the following table. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 RID PIX OwnerID AppletID AF Optional Data Elements AF = Application Function ID Java Card Specific Encoding The specification of the AID class supports enhanced interoperability in application selection and card management with a set of reserved encoding constants and corresponding standard decoding methods. This allows card applications to identify specific common roles in the card by examining the AID of applications. In the default encoding of the OwnerId and the Application ID the values 0x00 and 0xFF have been specified for this purpose. The default encoding implemented in this class uses these constants, implementations of alternative encoding schemes may use different values. The meaning of the special values can be asserted with: OwnerId.#isIssuer( )

This applet is controlled by the card issuer. It may be the applet management Applet, or an other card management related applet. The default coding value is 0XFF.

OwnerId.#isNotControled( )

This applet is not actively controlled by its owner as may be specified by its AID. It may be an applet that contains personal data related to and entered by the cardholder. The default coding value is 0X00.

AppletId.#isManager( )

This Applet is the card's applet management Applet or a delegated management Applet. The Application Management Applet must be owned by the card issuer. The default coding value is 0XFF.

AppletId.#isInformation( )

This applet provides information, e.g. pertaining to the cardholder. In addition to returning true in this method a cardholder data applet may indicate itself as not being controlled. The default coding value is 0X00.

Alternative encoding, e.g. to allow more space for optional data elements may be provided by overriding the relevant methods in this class. Any coding scheme should fully support the non optional data elements and their specific function codes.

Implementation Design

The AID class is implemented as wrapper around a data representation as a byte[ ]. Accessor methods and inner classes are specified to access and represent the types of the data elements that may be represented by an instance of the AID class. The implementation choice for the byte data representation is intended to improve the speed of retrieval of an AID. This retrieval may happen after the chip is reset when a list of all AIDs in the card may be assembled. Also, this data representation greatly simplifies the implementation of different encoding rules in possible subclasses.

The implementation of the classes to represent the component data elements similarly is as wrappers around byte[ ]. In the implementation instances of these classes share their data representation with their parent AID instance. With some increase in code complexity this design may be advantageous in speed and storage requirements. Security in the use of the AID is also enhanced, in that after the value of an AID instance has been committed to the non volatile card memory during Applet installation the information in it is never changed over the lifetime of an Applet. The implementation of AID and its component data type classes as a wrapper leverages the functionality provided by Buffer class that implements a generic wrapper around a byte[ ]. The Buffer is actually used as the base class for all these classes and supports the access to a shared byte[ ]. The shared byte[ ] holds the single constant data representation of the AID instance in the card memory. These data component types completely encapsulate the actual encoding and expose only the required semantic functionality.

The types defined for the data elements are:

1. AID.RID,

2. AID.OwnerId

3. AID.AppletId

4. AID.ConfigurationData

The classes for the AID component data elements also implement the Readable interface (via the base class ReadableBuffer) to facilitate retrieval as ISO files.

The AID class is an extension of the class and provides source code compatibility with existing applet implementations. Functionally, however, this class supersedes its base class completely.

Java Card Converter issues

The AID class implements the Serializable interface to support full card emulation with persistent in-card state. The implementation also provides methods to parse and produce a human readable form of the AID. These methods utilize in their implementation classes that are not part of the JCRE (StringTokenizer). With these features the implementation assumes the Java Card convertor to silently remove the interface and the non-convertible methods from the converted in-card class definition.

Note

This class, com.sun.smartcard.AID, extends the javacard.framework.AID class only to provide backward compatibility with existing card platform implementations, functionally this class replaces the original base class completely. Nested Class Summary Static class AID.AppletId   Represent the unique reference to an Applet that   is contained in an AID. Static class AID.ConfigurationData   Represent the Applet instance configuration data that may be contained in an AID. Static class AID.OwnerId   Represent the owner of an Applet instance that   is contained in an AID. Static class AID.RID   Represent the RID (Registered ID) part of an AID. Nested classes inherited from class com.sun.smartcard.util.Readable

Readable.WithStream Field Summary private data byte[ ]   The data representation of an AID is a byte[ ]. private SIZE static short   The size of an AID is fixed.

Constructor Summary protected AID( )   Create an Empty AID. AID(AID.RID rid)   Create an AID with a specific RID encoding. AID(byte[ ] encoding)   Create an AID from a specific full length encoding.

Method Summary (package private) getAppletId( ) AID.AppletId   Get the AppletId part from an AID. Protected getAssignedRID( ) AID.RID   Obtain the RID assigned to a card issuer or an application provider. AID.Configuration getConfiguration( ) Data   Obtain the configuration data part from the AID. byte getFunctionCode( )   Obtain a descriptor of the function of the applet conforming to ISO/IEC 14443 This method uses the default encoding, with the one byte code immediately following the AID.AppletId. (package private) getOwnerId( ) AID.OwnerId   Get the OwnerId part from an AID. (package private) getRID( ) AID.RID   Get the RID part from an AID. short getVersion( )   Obtain a descriptor value indicative of the version of the applet code. boolean matchId(byte[ ] encoding, short offset)   Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. boolean matchOwner(byte[ ] encoding, short offset)   Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. boolean matchRID(byte[ ] encoding, short offset)   Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. static AID parse(java.lang.String data)   Interpret a comma separated list of numbers in a string as an AID. short read(byte[ ] buffer, short offset, short dataskip, short length)   Append a serialized representation of the AID to a given byte[ ]. protected short readStateBytes(byte[ ] result, short off, short length)   Append the byte[ ] representation of the current Applet State to the AID's linear representation. protected void setdata(byte[ ] data)   Set the data representation for this AID to the specified array of bytes. java.lang.String toString( )   Represent the AID as a string of up to 16 hexadecimal integers. Methods inherited from class javacard.framework.AID Equals, equals, getBytes, partialEquals, RIDEquals Methods inherited from class java.lang.Object Clone, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait Field Detail SIZE private static final short SIZE

The size of an AID is fixed.

data

private byte[ ]

data

The data representation of an AID is a byte[ ]. This representation storage is shared by all the data elements that are encoded in it.

Constructor Detail

AID

protected

AID( )

Create an Empty AID. This constructor is for use in subclasses; subclasses constructed with this constructor need to use the set data( ) to initialize it properly. This definition allows the use of anonymous inner classes in the implementation of a specific Applet subclass to implement an AID. In this way the implementation of the readStateBytes( )method can be done with direct access to relevant state objects.

AID

public AID(AID.RID rid)

Create an AID with a specific RID encoding.

AID

public

AID(byte[ ] encoding)

Create an AID from a specific full length encoding. An encoding longer than 16 bytes is silently truncated, an encoding shorter than 5 bytes is an error.

Method Detail

parse

public static AIDparse(java.lang.String data)

Interpret a comma separated list of numbers in a string as an AID.

Note

This method uses classes that are not part of the JCRE and as a consequence will be skipped by the Java Card converter when building the in-card definition of the AID class. As a consequence none of the in-card methods can refer to this method.

toString

public

java.lang.String toString( )

Represent the AID as a string of up to 16 hexadecimal integers.

Overrides:

toString in class java.lang.Object

setdata

protected

final void setdata(byte[ ] data)

Set the data representation for this AID to the specified array of bytes.

getRID

final AID.RID

getRID( )

Get the RID part from an AID.

Returns:

-   -   an instance of AID.RID that is wrapped around the shared data         representation.         getAssignedRID         protected AID.RID         getAssignedRID( )

Obtain the RID assigned to a card issuer or an application provider. This method is intended for use in the constructor of a subclass of the AID to assure consistency of the data received with the representation specific to the sub class. To be used as intended this method should return the constant instance of a {link RID} class that is initialized with the RID prefix of AIDs that are decoded by the subclass.

Returns:

-   -   null, the base class does not check for its encoding as         compatible with a specific RID.         getOwnerId         final AID.OwnerId         getOwnerId( )

Get the OwnerId part from an AID.

Returns:

-   -   an instance of com.sun.smartcard.AID.OwnerID that is wrapped         around the shared data representation.         getAppletId         final AID.AppletId         getAppletId( )

Get the AppletId part from an AID.

Returns:

-   -   an instance of AID.AppletId that is wrapped around the shared         data representation.         getFunctionCode         public byte         getFunctionCode( )

Obtain a descriptor of the function of the applet conforming to ISO/IEC 14443 This method uses the default encoding, with the one byte code immediately following the AID.AppletId.

Returns:

-   -   a single byte containing the applet's function code.         getVersion         public short         getVersion( )

Obtain a descriptor value indicative of the version of the applet code. The default encoding does not include a version number; by default this method returns 0.

Returns:

-   -   0, the default encoding implemented in the base class does not         support a version.         getConfiguration         public AID.ConfigurationData         getConfiguration( )

Obtain the configuration data part from the AID. During applet instantiation this data may be used to initialize the applet instance configuration. In addition, this object may include configuration data relevant to instance specific security initialization.

readStateBytes

protected short

readStateBytes(byte[ ] result,

short off,

short length)

Append the byte[ ] representation of the current Applet State to the AID's linear representation.

The default implementation does nothing. Applets that want to transfer dynamic state information in the AID can do so by overriding this method with an implementation that calls the appropriate (public, package) methods in the Applet subclass.

The method signature is compatible with File.Readable.read( ).

read

public short

read(byte[ ] buffer,

-   -   short offset,         short dataskip,         short length)

Append a serialized representation of the AID to a given byte[ ]. This method may be used to use a READ BINARY COMMAND to access the value of the AID.

This implementation is based on the default JavaCard AID encoding rules and its result is obtained by appending the results of the inherited read( ) for AppletId getVersion( ) and getConfiguration( ), respectively, to the specified byte[ ]. When a subclass is used to implement an alternative encoding this method may need to be overri dden.

The signature of this method is specified by the core version of the Readable interface method and its implementation utilizes the similar lesser OO interface for its AppletId and Configuration components. A more sophisticated design could utilize the Readable.WithStream.read(com.sun.smartcard.util.Stream.Writer)method which has a more OO signature.

WARNING:

This implementation is incomplete as it does not provide error and parameter checking; it is provided as example, e.g. of the use of the Readable interface.

Specified by:

read in interface Readable

Parameters:

dataskip—***Ignored***

matchId

public final boolean

matchId(byte[ ] encoding,

short offset)

Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. The comparison is restricted to the data included in the AppletID. If no applet is found with a match using this method, the list of applets will be searched again for a match using the matchOwner(byte[ ], short) method.

Note:

While the default encoding as provided by this class performs the comparison on a prefix of the byte[ ], alternate encoding schemes, may be implemented by a sub class which could involve possible discontinuous segments of the encoding. When such alternative encoding is used the partial matching may actually require a full, 16 byte data representation to be presented as the argument to this method. In the default encoding only a prefix that contains the applet ID is needed.

The actual matching is performed by the Buffer.match(byte[ ] short) method.

The input parameters include an offset to facilitate matching of the AID against the raw content of the APDU buffer.

Parameters:

encoding—a byte containing a possible encoding of an AID.

offset—the offset in the specified byte[ ] where the actual AID encoding starts in the encoding

Returns:

true iff the appletID part of this AID matches the specified encoding.

matchOwner

public final boolean

matchOwner(byte[ ] encoding,

short offset)

Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. The comparison is restricted to the data included in the OwnerID; this method is typically called when no Applet instance is found that matches on the AppletID. If no applet is found with a match using this method, the list of applets will be searched again for a match using the matchRID(byte[ ], short)

Note:

While the default encoding as provided by this class performs the comparison on a prefix of the byte[ ], alternate encoding schemes, may be implemented by a sub class which could involve possible discontinuous segments of the encoding. When such alternative encoding is used the partial matching may actually require a full, 16 byte data representation to be presented as the argument to this method.

The actual matching is performed by the Buffer.match(byte[ ], short) method.

The input parameters include an offset to facilitate matching of the AID against the raw content of the APDU buffer.

Parameters:

encoding—a byte[ ] containing a possible encoding of an AID.

offset—the offset in the specified byte[ ] where the actual AID encoding starts in the

encoding

Returns:

true iff the OwnerID part of this AID part matches the specified encoding.

matchRID

public final boolean

matchRID(byte[ ] encoding,

short offset)

Compare the AID with a given encoding as used when the Applet instance that holds the AID is considered for “selection by AID”. The comparison is restricted to the data included in the RID part; this method is typically called when no Applet is found that matches on the Owner ID. If no Applet is found with a match using this method, then no applets in the card exist that match the given ID and the select by AID command will return a failure.

The actual matching is performed by the Buffer.match(byte[ ], short) method.

The input parameters include an offset to facilitate matching of the AID against the raw content of the APDU buffer.

Note:

While the default encoding as provided by this class performs the comparison on a prefix of the byte[ ], alternate encoding schemes, may be implemented by a sub class which could involve possible discontinuous segments of the encoding. When such encoding is used partial matching may require a full, 16 byte encoding to be presented as the argument to this method.

Parameters:

encoding—a byte containing a possible encoding of an AID.

offset—the offset in the specified byte where the actual AID encoding starts in the encoding

Returns:

true iff the RID part of this AID matches the specified encoding.

Appendix B

Class AID.RID

All Implemented Interfaces:

Readable

Enclosing class:

AID

public static class AID.RID

extends ReadableBuffer

Represent the RID (Registered ID) part of an AID.

This class is a wrapper around a serialized data representation, which may be shared with the parent AID.

A generic wrapper class for byte[ ], ReadableBuffer is used as a base class.

Nested Class Summary

Nested classes inherited from class com.sun.smartcard.util.Readable

Readable.WithStream

Field Summary

Fields inherited from class com.sun.smartcard.util.Bytes Constructor Summary Private AID.RID( )   Construct an empty instance, for exclusive use by the   AID class. AID.RID(byte[ ] encoding)   Construct an instance with a given data representation.

Method Summary protected getData( ) byte[ ]   Share the data with the enclosing class. short getLength( )   Get the length of the data in the byte array for a RID (5). Methods inherited from class com.sun.smartcard.util.ReadableBuffer read Methods inherited from class com.sun.smartcard.util.Buffer getByteAt, getBytes, getDataSize, getFullyAt, getPrefixSkip, getSize, isValidIndex, match, match, match, setByteAt, setData Methods inherited from class com.sun.smartcard.util.Bytes equals, getBytes, getBytes, setBytes Methods inherited from class java.lang.Object clone, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait Constructor Detail AID.RID public AID.RID(byte[ ] encoding)

Construct an instance with a given data representation.

AID.RID

private AID.RID( )

Construct an empty instance, for exclusive use by the AID class.

Method Detail

getLength

public final short getLength( )

Get the length of the data in the byte array for a RID (5). The size of the RID is defined in ISO/IEC 7816-5

Overrides:

-   -   getLength in class Bytes

Returns:

-   -   5         getData         protected final byte[ ] getData( )

Share the data with the enclosing class.

Overrides:

getData in class Bytes

Appendix C

Class AID.OwnerId

All Implemented Interfaces:

Readable

Enclosing class:

AID

public static class AID.OwnerId

extends ReadableBuffer

Represent the owner of an Applet instance that is contained in an AID. The owner of data in a Java Card Memory specifies the firewall that controls access to data.

This class is a wrapper around a serialized data representation, which may be shared with the parent AID. A generic wrapper class for byte[ ], ReadableBuffer is used as a base class.

Nested Class Summary

Nested classes inherited from class com.sun.smartcard.util.Readable

Readable.WithStream

Field Summary

Fields inherited from class com.sun.smartcard.util.Bytes Constructor Summary private AID.OwnerId( )   Construct an empty instance, for exclusive use by the AID class as wrapper on a shared data representation. AID.OwnerId(byte[ ] code)   Construct an instance as wrapper on the specified data   representation.

Method Summary short getLength( )   Get the length of the data in the byte array for the Owner   part of the AID. (package getRID( ) private)   Get the RID part from the OwnerID. AID.RID boolean isIssuer( )   Test for Card Issuer reserved value encoding. boolean isNotControled( )   Test for “not owner controlled” reserved value encoding. Methods inherited from class com.sun.smartcard.util.ReadableBuffer Read Methods inherited from class com.sun.smartcard.util.Buffer getByteAt, getBytes, getDataSize, getFullyAt, getPrefixSkip, getSize, isValidIndex, match, match, match, setByteAt, setData Methods inherited from class com.sun.smartcard.util.Bytes equals, getBytes, getBytes, getData, setBytes Methods inherited from class java.lang.Object clone, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait Constructor Detail AID.OwnerId public AID.OwnerId(byte[ ] code)

Construct an instance as wrapper on the specified data representation. This constructor is implemented by the constructor of the ReadableBuffer with the same signature.

AID.OwnerId

private AID.OwnerId( )

Construct an empty instance, for exclusive use by the AID class as wrapper on a shared data representation.

Method Detail

getLength

public short getLength( )

Get the length of the data in the byte array for the Owner part of the AID. This method implements the default encoding rules, with the OwnerId being a one byte extension of the RID and therefore returns the value six.

Overrides:

getLength in class Bytes

Returns:

6

getRID

final AID.RID getRID( )

Get the RID part from the OwnerID.

isIssuer

public final boolean isIssuer( )

Test for Card Issuer reserved value encoding.

isNotControled

public final boolean isNotControled( )

Test for “not owner controlled” reserved value encoding.

Appendix D

Class AID.AppletId

All Implemented Interfaces:

Readable

Enclosing class:

AID

public static class AID.AppletId

extends ReadableBuffer

Represent the unique reference to an Applet that is contained in an AID. Guaranteeing the uniqueness of an applet ID is left to the owner of the applet. The default implementation uses one additional byte appended to the encoding of the Owner.

This class is a wrapper around a serialized data representation, which may be shared with the parent AID.

A generic wrapper class for byte[ ], ReadableBuffer is used as a base class.

Nested Class Summary

Nested classes inherited from class com.sun.smartcard.util.Readable

Readable.WithStream

Field Summary

Fields inherited from class com.sun.smartcard.util.Bytes Constructor Summary private AID.AppletId( )   Construct an empty instance, for exclusive use by the AID   class. AID.AppletId(byte[ ] code)   Construct an instance with a given data representation.

Method Summary short getLength( )   Get the length of the data in the byte array for the AppletId component of the AID. (package getOwnerId( ) private)   Get the Owner Identifier contained in the applet AID.OwnerId   identifier. boolean isInformation( )   Test for “not owner controlled” reserved value   encoding. boolean isManager( )   Test for Card Issuer reserved value encoding. Methods inherited from class com.sun.smartcard.util.ReadableBuffer read Methods inherited from class com.sun.smartcard.util.Buffer getByteAt, getBytes, getDataSize, getFullyAt, getPrefixSkip, getSize, isValidIndex, match, match, match, setByteAt, setData Methods inherited from class com.sun.smartcard.util.Bytes equals, getBytes, getBytes, getData, setBytes Methods inherited from class java.lang.Object clone, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait Constructor Detail AID.AppletId public AID.AppletId(byte[ ] code)

Construct an instance with a given data representation.

AID.AppletId

private AID.AppletId( )

Construct an empty instance, for exclusive use by the AID class.

Method Detail

getLength

public short getLength( )

Get the length of the data in the byte array for the AppletId component of the AID. This method implements the default encoding rules, with the AppletId being a one byte extension of the OwnerID and therefore returns a value of seven.

Overrides:

getLength in class Bytes

Returns:

7

getOwnerId

final AID.OwnerId getOwnerId( )

Get the Owner Identifier contained in the applet identifier.

isManager

public final boolean isManager( )

Test for Card Issuer reserved value encoding.

isInformation

public final boolean isInformation( )

Test for “not owner controlled” reserved value encoding.

Appendix E

Class AID.ConfigurationData

All Implemented Interfaces:

Readable

Direct Known Subclasses:

CardHolderDataApplet.CardHolderDataConfiguration

Enclosing class:

AID

public abstract static class AID.ConfigurationData

extends ReadableBuffer

Represent the Applet instance configuration data that may be contained in an AID. The configuration data, when present in an AID may be used when the Applet is instantiated to configure its components. For instance, the size of an array of object that represent a set of user data may be specified in the configuration. This class to be extended when a configuration is present on the encoding of an AID.

This class is a wrapper around a serialized data representation, which may be shared with the parent AID. A generic wrapper class for byte[ ], ReadableBuffer is used as a base class;

The current version of the implementation does not support configuration in the default encoding, however in a more mature version this might well be different.

Nested Class Summary

Nested classes inherited from class com.sun.smartcard.util.Readable

Readable.WithStream

Field Summary

Fields inherited from class com.sun.smartcard.util.Bytes Constructor Summary protected AID.ConfigurationData( )   Construct a default instance. AID.ConfigurationData(byte[ ] code)   Construct an instance as a wrapper around a   given data representation

Method Summary short getLength( )   Specify the length of the data (byte[ ]) that represents the   configuration data. short getPrefixSkip( )   Skip the initial portion of the AID encoding Methods inherited from class com.sun.smartcard.util.ReadableBuffer read Methods inherited from class com.sun.smartcard.util.Buffer getByteAt, getBytes, getDataSize, getFullyAt, getSize, isValidIndex, match, match, match, setByteAt, setData Methods inherited from class com.sun.smartcard.util.Bytes equals, getBytes, getBytes, getData, setBytes Methods inherited from class java.lang.Object clone, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait Constructor Detail AID.ConfigurationData public AID.ConfigurationData (byte[ ] code)

Construct an instance as a wrapper around a given data representation. This constructor is implemented by the constructor of the ReadableBuffer with the same signature. The data specified by the argument is not copied.

AID.ConfigurationData

protected AID.ConfigurationData( )

Construct a default instance.

Method Detail

getLength

public short getLength( )

Specify the length of the data (byte[ ])that represents the configuration data. The default encoding does not contain any configuration data, so its length is 0.

Overrides:

getLength in class Bytes

getPrefixSkip

public short getPrefixSkip( )

Skip the initial portion of the AID encoding. The value returned is in accordance with the default encoding and is equal to the length of the AppletID) representation plus one byte for the function code.

Overrides:

getPrefixSkip in class Buffer

Returns:

the offset in the AID data representation where the configuration data can be found.

Appendix F

Class AIDInterpreter

All Implemented Interfaces:

java.lang.Cloneable

public class AIDInterpreter

extends java.lang.Object

implements java.lang.Cloneable

Provide access to the data describing an Applet as specified by the AID. This class is intended for use in terminals, to provide detailed information about an applet in a card. Applet information is partially encoded in the AID data string read from the card; additional data regarding the Applet may be embedded in a sub class derived from this class or in part retrieved on the internet for instance using references embedded in the sub class implementation. The attributes defined for this class provide explicit support for internationalization of the terminal code.

Together with the in-card companion class com.sun.smarcard.AID this class is a key component in providing generic application management support for the Java Card platform. The class provides support for the dynamic configuration of card terminals.

The definition of sub classes of this class, their class files, may be stored at web-accessible repositories. A class naming scheme is implemented in this class that is based on the internationally registered identifier (RID) that is included in each AID encoding. A factory method is provided to instantiate a class based on a specific RID using this naming scheme. The class definition register may be maintained by an international organization like Java Card Forum.

By default the data describing the applet and its in-terminal components is made available by this class as a Java attribute list. Each attribute consist of an attribute name and attribute value both attribute parts being a Java String. Sub classes may define additional, e.g method call based, access to part of the data.

The following types of properties are specified here:

-   -   1. Owner properties     -   2. Applet Properties     -   3. Terminal properties         Card application attributes

The following attribute names are defined by this class. This class actually supports a basic set of attributes; a sub-class may implement support for additional attributes. Attributes that are not supported have a value of null.

Owner

The name of the organizational or business unit that is responsible for the Applet.

Owner.code

The hexadecimal representation of the encoding of the ownerID.

Owner.URL

A URL referring to a description of the organizational or business unit that is responsible for the Applet.

Owner.Logo

A URL referring to an image characterizing the organizational or business unit that is responsible for the Applet.

Owner.BackOfficeURI

A URI referring to the back office (application management system) operated by the Applet owner to manage the use of the Applet in the card.

Applet.Function.DescriptionURL

A web page describing the function of the applet in a default language.

Applet.Function

A brief description of the Applet function in a default language.

Applet.Function.+lang+

A brief description of the Applet function in the language specified by +lang+ (encoded as ISO language identifiers).

Applet.CAPFile.URL

A URL specifying the name of the file containing the downloadable code for the applet.

Applet.Title

A summary description of the Applet.

Applet.Title.+lang+

A summary description of the Applet in the language specified by +lang+.

Applet.Proxy.Count

The number of application proxies that may be used to interact with the applet. Each proxy may be offering a different set of functions.

Applet.Proxy.Title.+count+

A summary description of the application proxy.

Applet.Proxy.Title.+count+.+lang+

A summary description of the application proxy in the language specified by +lang+.

Applet.Proxy.CardApplicationServiceAPI.+count+

The class name of the Java interface that specifies the functional interface of the specific application proxy.

Applet.Proxy.Class.+count+

The class name of a specific application proxy.

Applet.Proxy.Jar.+count+

The URL of ajar file that contains the proxy java class and supporting classes for a specific application proxy.

Applet.Function.Code

The hex representation of the one byte Applet function code as defined in ISO/IEC 14344.

Applet.Function.ProxyClass

A Java class name of the specific class that can be used to communicate optimally with the applet and its backoffice. This class in general wil be provided by the Application Provider; instantiating the class in a terminal may be subject to commercial agreements.

Applet.Function.ProxyClass.GenericInterface

A Java class name of the specific interface that may be used to communicate with the applet to obtain the shared functionality as defined by the Function code.

Applet.Function.ProxyClass.GenericInterface.Implementation

A Java class name of an implementation of the generic interface that may be used to communicate with the applet to obtain the shared functionality as defined by the Function code. The instantiation of this class in the terminal should be possible without commercial restrictions.

Applet.Version

The decimal representation of the version in a “major.minor” notation. This is 0.0 if not supported by the AID.

RID

The name of the legal entity that has obtained the RID.

RID.code

The hexadecimal representation of the RID

RID.URL

A URL referring to a description of the legal entity that has obtained the RID.

PIX

The hexadecimal representation of the PIX. Field Summary private AID aid   The AID being interpreted. Static java.lang. AID_CLASS_NAME_PREFIX String Static java.lang. AID_INTERPRETER_PACKAGE_PATH String[ ]   The name of a JavaCard special package for Issuer specific versions of this class.

Constructor Summary AIDInterpreter( )

Method Summary Method Summary protected static AID getAID(AID.RID rid)   Get an instance of an AID sub class as appropriate for the applet. protected getAIDPackageList( ) static java.lang.String[ ]   Get a list of all the package names that may contain the definition of an appropriate AIDInterpreter class definition. java.lang.String[ ] getAppletStateDataPropertyNames( )   Obtain the attribute names for applet data that may be included in the AID. java.lang.String GetAppletString(short stringreference)   Obtain a string that has been removed from the applet code by the conversion to Java Card ByteCode. java.util.Properties GetAsProperties( )   Interpret the content of an AID as a list of name value pairs. AIDInterpreter GetCardEncodingInterpreter(byte[ ] encoding)   Clone the interpreter initialized with the encoding of a compatible AID as may be obtained from the card. java.lang.String[ ] GetConfigurationPropertyNames( )   Obtain the list of attribute names that describe the values that may be present in the configuration part of the AID. (package private) makeOne(AID.RID rid) static AIDInterpreter   Create an instance of a derived class for the AID Interpreter, as defined by the specified RID. static AIDInterpreter makeOne (byte[ ] encoding)   Create an instance of the AID that fits a specified AID encoding. Methods inherited from class java.lang.Object Clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait Field Detail AID_INTERPRETER_PACKAGE_PATH public static final java.lang.String[ ] AID_INTERPRETER_PACKAGE_PATH

The name of a JavaCard special package for Issuer specific versions of this class.

AID_CLASS_NAME_PREFIX

public static final java.lang.String AID_CLASS_NAME_PREFIX

aid

private AID aid

The AID being interpreted.

Constructor Detail

AIDInterpreter

public AIDInterpreter( )

Method Detail

makeOne

static final AIDInterpreter makeOne(AID.RID rid)

Create an instance of a derived class for the AID Interpreter, as defined by the specified RID.

The interpreter classes are located in a Java package with the special name “javacard.aidinterpreters”.

Note:

This method is never called inside the card.

getAIDPackageList

protected static java.lang.String[ ] getAIDPackageList( )

Get a list of all the package names that may contain the definition of an appropriate AIDInterpreter class definition.

makeOne

public static final AIDInterprete makeOne(byte[ ] encoding)

Create an instance of the AID that fits a specified AID encoding.

Note:

This method is never called inside the card. The in-card implementation of this class may dispense with it.

getAID

protected static AID getAID(AID.RID rid)

Get an instance of an AID sub class as appropriate for the applet. This class will be defined by the application provider as part of the applet code. Instances of this specific class will both be used in the card and outside it, as is demonstrated by the interpreter class.

getCardEncodingInterpreter

public AIDInterpreter getCardEncodingInterpreter(byte[ ] encoding)

Clone the interpreter initialized with the encoding of a compatible AID as may be obtained from the card. A compatible AID encoding matches the Applet ID.

Returns:

-   -   null if the specified encoding does not match the application         ID.         getAsProperties         public java.util.Properties getAsProperties( )

Interpret the content of an AID as a list of name value pairs. This method returns a properties object initialized with the properties available by interpreting the default AID encoding. Additional properties may be provided in a sub class, e.g by adding properties to the result of this function in the constructor.

getConfigurationPropertyNames

public java.lang.String[ ] getConfigurationPropertyNames( )

Obtain the list of attribute names that describe the values that may be present in the configuration part of the AID. This method is for out of card use, providing interoperable interpretation of the result in terminals. This method uses the default encoding.

getAppletStateDataPropertyNames

public java.lang.String[ ] getAppletStateDataPropertyNames( )

Obtain the attribute names for applet data that may be included in the AID. By default this method does nothing and returns null. A sub class that is intended to interpret an AID that contains optional state data in the encoding of the AID should override this method.

getAppletString

public java.lang.String getAppletString(short stringreference)

Obtain a string that has been removed from the applet code by the conversion to Java Card ByteCode. This method allows the limited support of the Java String class in Java Card applet code whereby the strings embedded in the code are replaced by a numeric reference. The numeric reference may be returned to the terminal in a response and subsequently used as index into an array of strings that may be made available to the card terminal. 

1. A method for installing an application onto a smart card comprising: providing an application identifier (AID) for the application, wherein said AID comprises at least one customization parameter for the application to be installed; instantiating the application onto the smart card; storing the AID for the application onto the card; and configuring the application in accordance with the stored AID, wherein the application is configured in accordance with said at least one customization parameter.
 2. The method of claim 1, wherein the application comprises an AID interpreter.
 3. The method of claim 2, further comprising passing the AID to the AID interpreter to allow the AID interpreter to perform the storing of the AID for the application onto the card.
 4. The method of claim 2, wherein configuring the application comprises: accessing the stored AID with the AID interpreter; and extracting said at least one customization parameter from the stored AID using the AID interpreter.
 5. The method of claim 2, wherein the AID is stored onto the card as a byte array that is accessed via the AID interpreter.
 6. The method of claim 2, wherein instantiating the application comprises instantiating the AID interpreter by calling a method on the application.
 7. The method of claim 1, wherein storing the AID for the application onto the card is performed as part of initialization of the application.
 8. The method of claim 1, wherein the application comprises a set of Java classes and the smart card conforms to the JavaCard API.
 9. The method of claim 1, wherein said at least one customization parameter relates to one or more attributes of resources available to the application.
 10. The method of claim 1, wherein said at least one customization parameter relates to one or more attributes of cryptographic facilities to be used by the application.
 11. The method of claim 1, wherein said at least one customization parameter is indicative of a level of service to be made available to a cardholder in transactions involving the application.
 12. An apparatus for installing an application onto a smart card comprising: an application identifier (AID) for the application, wherein said AID comprises at least one customization parameter for the application to be installed; and an install facility operable to instantiate the application onto the smart card and to store the AID for the application onto the card, wherein the application is configured in accordance with said at least one customization parameter from the stored AID.
 13. The apparatus of claim 12, wherein the application comprises an AID interpreter.
 14. The apparatus of claim 13, wherein the AID is passed to the AID interpreter to allow the AID interpreter to store the AID for the application onto the card.
 15. The apparatus of claim 13, wherein the application is configured by accessing the stored AID with the AID interpreter and extracting said at least one customization parameter from the stored AID using the AID interpreter.
 16. The apparatus of claim 13, wherein the AID is stored onto the card as a byte array that is accessed via the AID interpreter.
 17. The apparatus of claim 13, wherein instantiating the application comprises instantiating the AID interpreter by calling a method on the application.
 18. The apparatus of claim 12, wherein the AID for an application is stored onto the card as part of initialization of the application.
 19. The apparatus of claim 12, wherein the application comprises a set of Java classes and the smart card conforms to the JavaCard API.
 20. An apparatus for installing an application onto a smart card comprising: means for providing an application identifier (AID) for the application, wherein said AID comprises at least one customization parameter for the application to be installed; means for instantiating the application onto the smart card; means for storing the AID for the application onto the card; and means for configuring the application in accordance with the stored AID, wherein the application is configured in accordance with said at least one customization parameter.
 21. A computer program product comprising instructions on a medium, wherein said instructions when loaded into a machine cause the machine to install an application onto a smart card by: providing an application identifier (AID) for the application, wherein said AID comprises at least one customization parameter for the application to be installed; instantiating the application onto the smart card; storing the AID for the application onto the card; and configuring the application in accordance with the stored AID, wherein the application is configured in accordance with said at least one customization parameter.
 22. The computer program product of claim 21, wherein the application comprises an AID interpreter.
 23. The computer program product of claim 22, wherein the instructions further cause the machine to pass the AID to the AID interpreter to allow the AID interpreter to perform the storing of the AID for the application onto the card.
 24. The computer program product of claim 22, wherein configuring the application comprises: accessing the stored AID with the AID interpreter; and extracting said at least one customization parameter from the stored AID using the AID interpreter.
 25. The computer program product of claim 22, wherein the AID is stored onto the card as a byte array that is accessed via the AID interpreter.
 26. The computer program product of claim 22, wherein instantiating the application comprises instantiating the AID interpreter by calling a method on the application.
 27. The computer program product of claim 21, wherein storing the AID for the application onto the card is performed as part of initialization of the application.
 28. The computer program product of claim 21, wherein the application comprises a set of Java classes and the smart card conforms to the JavaCard API.
 29. The computer program product of claim 21, wherein said at least one customization parameter relates to one or more attributes of resources available to the application.
 30. The computer program product of claim 21, wherein said at least one customization parameter relates to one or more attributes of cryptographic facilities to be used by the application.
 31. The computer program product of claim 21, wherein said at least one customization parameter is indicative of a level of service to be made available to a cardholder in transactions involving the application. 